You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Kalnichevski, Oleg" <ol...@bearingpoint.com> on 2003/07/10 10:47:20 UTC
[PATCH] Multiple transfer encodings are still not handled properly
Mike,
It looks like out recent patch is still not quite correct in handling multiple transfer encodings. I have re-read the relevant sections of the RFC 2616 on this issue and found out the following:
Multiple transfer encodings are not supposed to be declared in separate 'Transfer-Encoding' headers
Transfer-Encoding: gzip
Transfer-Encoding: whatever
Transfer-Encoding: chunked
Multiple transfer encodings are supposed to be declared in as a comma separated list in one header
Transfer-Encoding: gzip, whatever, chunked
I attache the patch that should correct the bug
Re: [PATCH] Multiple transfer encodings are still not handled properly
Posted by Michael Becke <be...@u.washington.edu>.
Which section of the RFC talks about this?
Mike
Kalnichevski, Oleg wrote:
> Mike,
> It looks like out recent patch is still not quite correct in handling multiple transfer encodings. I have re-read the relevant sections of the RFC 2616 on this issue and found out the following:
>
> Multiple transfer encodings are not supposed to be declared in separate 'Transfer-Encoding' headers
>
> Transfer-Encoding: gzip
> Transfer-Encoding: whatever
> Transfer-Encoding: chunked
>
> Multiple transfer encodings are supposed to be declared in as a comma separated list in one header
>
> Transfer-Encoding: gzip, whatever, chunked
>
> I attache the patch that should correct the bug
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org