[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054831#comment-18054831
 ] 

Joakim Erdfelt commented on HTTPCLIENT-2409:
--------------------------------------------

>> If your client does automatic response content decoding, and doesn't change 
>> the representation of that response content in it's headers, then you have a 
>> client that is inappropriate to use in a proxy scenario.

> Anyways, proxies are expected to re-write the response to drop hop-by-hop 
>headers as per the HTTP specification. Likewise, they can also be expected to 
>update the representation of that response content in it's headers

Considering that we are talking about `Content-Encoding` and `Content-Length`, 
we are not talking about hop-by-hop headers.

[https://datatracker.ietf.org/doc/html/rfc2616#section-13.5.1]

The defined hop-by-hop headers (for HTTP/1.1) are ...
 * Connection
 * Keep-Alive
 * Proxy-Authenticate
 * Proxy-Authorization
 * TE
 * Trailers
 * Transfer-Encoding
 * Upgrade

The representation of the response content is not a hop-by-hop concern.

 

> Content-Length header not removed/modified when decompressing
> -------------------------------------------------------------
>
>                 Key: HTTPCLIENT-2409
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2409
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 5.6
>            Reporter: Cristian Vat
>            Priority: Major
>
> When decompressing gzip or other compression schemes the Content-Length 
> header is not modified/removed anymore as it was before, this can lead to 
> unexpected behaviors like truncation depending on caller behavior.
>  
> Originally thought it was a spring issue with RestClient as 
> https://github.com/spring-projects/spring-framework/issues/36064
> Summary:
>  * Content-Encoding: gzip
>  * Content-Length: 9075
>  * actual read content if reading fully: 56815
>  
> It's a combination of Spring and HttpClient behaviors but it lead to 
> truncation at the compressed content length.
> I checked JDK HttpClient and Jetty HttpClient and they remove the 
> Content-Length header if doing decompression.
> The same seems to have been the case in HttpComponents HttpClient but then 
> the code that removed the headers was removed on 20th October in 
> [https://github.com/apache/httpcomponents-client/commit/56122fd33fb8a67d23369a81f6e1d89aabf4ba10]
>  ?
>  
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to