httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <>
Subject Re: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header
Date Tue, 10 Mar 2015 09:27:13 GMT
Am 09.03.2015 um 15:57 schrieb
> Hi,
> I have some problems using mod_deflate to decompress requests.
> I am using a apache 2.4 as a reverse proxy on Red Hat Enterprise Linux Server release
6.4 (Santiago). Within this apache I have to decompress requests and compress the answers.
> To do this for some specific requests I defined a location:
> <Location /web-services>
>    SetInputFilter DEFLATE	
>    SetOutputFilter DEFLATE	
> </Location>
> I got the result, that the request have been decompressed, but the header Content-Encoding
gzip is still set causing problems on the next server.
> So I removed the Content-Encoding header using mod_headers:
> <Location /web-services>
>    RequestHeader unset Content-Encoding
>    SetInputFilter DEFLATE	
>    SetOutputFilter DEFLATE	
>    Header set Content-Encoding gzip
> </Location>
> As a result in the request the Content-Encoding is not set anymore. But the request is
still compressed.
> The manual of mod_deflate says that only requests with the header Content-Encoding gzip
are decompressed. So it seems that mod_headers is executed before mod_deflate.
> So basically either the decompression is done and the header is not changed or the header
is changed but the decompression is not done.
> Is there any way to decompress the request and remove the Content-Encoding gzip header?

mod_deflate does contain code to fix the content-encoding header. Could 
you provide info, how exactly your content-encoding request header looks 
like without and with inflation (no mod_headers manipulation)? Try to 
get the info directly on the reverse proxy, not on the backend, e.g. by 
logging %{Content-Encoding}i in the proxy access log.

mod_deflate did get quite a few fixes lately in 2.4. None of them was 
directly related to fixing the content-encoding header, but maybe you 
triger some other error path. Not likely, because the header fixing is 
done early but maybe still possible. Which version is your Apache httpd?



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message