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)

Is this accurate?


Thanks again,


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