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 the HTTP/1.1 proxies we have tested passed
all test cases with chunked requests. Some crashed.

So, regardless of the official position, this feature is not
well supported (yet?). Based on anecdotal evidence related to our
tests, many implementors seem to be taken by surprise: "ah, looks like
this MUST be supported, but we did not know that!".

To answer one of your questions, a client can reasonably
expect that their chunked POST will fail if there is a proxy in the
way. Hopefully, the situation will improve once we get implementors
attention.

Alex.

P.S. You can also find a few real-world cases with chunked requests:
http://www.google.com/search?q=chunked+request
http://www.google.com/search?q=chunked+request+Microsoft

On Mon, 10 Jun 2002, Mark Nottingham wrote:

> 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/
>
>
>