Search the web
Sign In
New User? Sign Up
http-compliance · discussion about HTTP compliance testing and tests
? Already a member? Sign in to Yahoo!

Yahoo! Groups Tips

Did you know...
Real people. Real stories. See how Yahoo! Groups impacts members worldwide.

Best of Y! Groups

   Check them out and nominate your group.
Having problems with message search? Fill out this form to ensure your group is one of the first to be migrated to the new message search system.

Messages

  Messages Help
Advanced
Chunked POST   Message List  
Reply | Forward Message #93 of 117 |
Re: [http-compliance] Chunked POST

On Tue, 11 Jun 2002, Mark Nottingham wrote:

> Thanks. So, from a client perspective, they might expect any of the
> following behaviours when sending a chunked POST;
> a) success
> b) 411 Length Required
> c) 5xx error
> d) connection close (proxy crashed or other fatal error)

e) a malformed/invalid message reaches the server (proxy
corrupts message body and/or headers because it does
not understand what is going on); the server reaction
is difficult to predict, but it might include "200 OK"
if the server/CGI was not able to detect that the message
got corrupted and, for example, interpreted a portion of
the POSTed data only (the worst case).

Alex.

> ----- Original Message -----
> From: "Carl Kugler" <kugler@...>
> To: <http-compliance@yahoogroups.com>
> Sent: Tuesday, June 11, 2002 8:28 AM
> Subject: Re: [http-compliance] Chunked POST
>
>
> > Mark-
> >
> > I can't speak for the official position. The primary interoperability
> > problem is due to CGI 1.1 (and earlier). CGI REQUIRES a CONTENT-LENGTH.
> > Some servlet engines also have this restriction. Another possible
> problem
> > is due to proxies: a proxy server is allowed to coalesce all the chunks
> > into a monolithic request. In practice, you never see this, because it
> > could require ulimited buffer space on the proxy server, and because it
> > has bad effects on response time.
> >
> > -Carl
> >
> >
> >
> >
> >
> >
> > "Mark Nottingham" <mnot@...>
> > 06/10/2002 10:14 PM
> > Please respond to http-compliance
> >
> >
> > To: <http-compliance@yahoogroups.com>
> > cc:
> > Subject: [http-compliance] Chunked POST
> >
> >
> > Can someone remind me what the state of the art is re: chunked POST?
> From
> > what I can see, it's allowed, but there's not a good interoperability
> > story with 1.0, so it's mostly avoided.
> >
> > What's the official position, and what can a client reasonably expect if
> > they chunk a POST and there's a 1.1 server somewhere in the message
> path?
> >
> > Thanks,
> >
> > --
> > Mark Nottingham
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > http-compliance-unsubscribe@egroups.com
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> >
>
>
>
> To unsubscribe from this group, send an email to:
> http-compliance-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>




Tue Jun 11, 2002 5:07 pm

rousskov@...
Send Email Send Email

Forward
Message #93 of 117 |
Expand Messages Author Sort by Date

Can someone remind me what the state of the art is re: chunked POST? From what I can see, it's allowed, but there's not a good interoperability story with 1.0,...
Mark Nottingham
mnotting
Online Now Send Email
Jun 11, 2002
4:12 am

Mark- I can't speak for the official position. The primary interoperability problem is due to CGI 1.1 (and earlier). CGI REQUIRES a CONTENT-LENGTH. Some...
Carl Kugler
carlk3
Offline Send Email
Jun 11, 2002
3:28 pm

Mark, FYI: Since supporting chunked encoded _messages_ is a MUST, our HTTP compliance test suite has test cases that use chunked _requests_. So far, none of...
Alex Rousskov
rousskov@...
Send Email
Jun 11, 2002
4:17 pm

Thanks. So, from a client perspective, they might expect any of the following behaviours when sending a chunked POST; a) success b) 411 Length Required c) 5xx...
Mark Nottingham
mnotting
Online Now Send Email
Jun 11, 2002
4:59 pm

... e) a malformed/invalid message reaches the server (proxy corrupts message body and/or headers because it does not understand what is going on); the server...
Alex Rousskov
rousskov@...
Send Email
Jun 11, 2002
5:07 pm

[Alex Rousskov: Tue, Jun 11, 2002 at 11:07:10AM -0600] ... f) 100 continue -Patrick...
Patrick McManus
mcmanus@...
Send Email
Jun 11, 2002
5:14 pm

... g) nothing (i.e., the recipient [erroneously] waits for more data, without sending 100 continue) Alex....
Alex Rousskov
rousskov@...
Send Email
Jun 11, 2002
5:24 pm

h) 413 Request Entity Too Large. -Carl Alex Rousskov <rousskov@...> 06/11/2002 11:24 AM Please respond to http-compliance To:...
Carl Kugler
carlk3
Offline Send Email
Jun 11, 2002
5:37 pm
Advanced

Copyright © 2009 Yahoo! Inc. All rights reserved.
Privacy Policy - Terms of Service - Guidelines - Help