06/11/2002 11:24 AM
Please respond to http-compliance
To: http-compliance@yahoogroups.com
cc:
Subject: Re: [http-compliance] Chunked POST
On Tue, 11 Jun 2002, Patrick McManus wrote:
> [Alex Rousskov: Tue, Jun 11, 2002 at 11:07:10AM -0600]
> > 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).
>
> f) 100 continue
g) nothing (i.e., the recipient [erroneously] waits for more data,
without sending 100 continue)
Alex.
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Will You Find True Love?
Will You Meet the One?
Free Love Reading by phone!
http://us.click.yahoo.com/Deo18C/zDLEAA/Ey.GAA/CefplB/TM
---------------------------------------------------------------------~->
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/
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- 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...
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@...
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...
... 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@...
Jun 11, 2002 5:07 pm
[Alex Rousskov: Tue, Jun 11, 2002 at 11:07:10AM -0600] ... f) 100 continue -Patrick...
Patrick McManus
mcmanus@...
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@...
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:...
Having problems with message search?
Offline 
Send Email
