Re: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header
On Tue, Mar 10, 2015 at 10:25 AM, Yann Ylavic wrote: > Hi Dennis, > > On Tue, Mar 10, 2015 at 10:07 AM, wrote: >> >> But my current problem is that I can't get the decompression of the requests >> working. > > SetInputFilter INFLATE (instead of DEFLATE)? No, it's an output filter only, the right one is indeed DEFLATE (which inflates). Sorry for the noise. > > Regards, > Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header
Am 09.03.2015 um 15:57 schrieb dennis.luna...@t-systems.com:
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:
SetInputFilter DEFLATE
SetOutputFilter DEFLATE
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:
RequestHeader unset Content-Encoding
SetInputFilter DEFLATE
SetOutputFilter DEFLATE
Header set Content-Encoding gzip
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?
Regards,
Rainer
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header
Hi Dennis, On Tue, Mar 10, 2015 at 10:07 AM, wrote: > > But my current problem is that I can't get the decompression of the requests > working. SetInputFilter INFLATE (instead of DEFLATE)? Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
RE: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header
Hi James, yes you are correct, I also have to remove the Accept-Encoding header later for the response compression. But my current problem is that I can't get the decompression of the requests working. Regards, Dennis -Original Message- From: James Smith [mailto:j...@sanger.ac.uk] Sent: Montag, 9. März 2015 16:00 To: users@httpd.apache.org Subject: Re: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header Wrong header... RequestHeader unset Accept-Encoding is the way to stop the backend compressing the request... On 09/03/2015 14:57, dennis.luna...@t-systems.com wrote: > 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: > >SetInputFilter DEFLATE >SetOutputFilter DEFLATE > > 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: > >RequestHeader unset Content-Encoding >SetInputFilter DEFLATE >SetOutputFilter DEFLATE >Header set Content-Encoding gzip > > 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? > > Regards, > Dennis > > - > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Decompress requests using mod_deflate and uset Content-Encoding header
Wrong header... RequestHeader unset Accept-Encoding is the way to stop the backend compressing the request... On 09/03/2015 14:57, dennis.luna...@t-systems.com wrote: 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: SetInputFilter DEFLATE SetOutputFilter DEFLATE 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: RequestHeader unset Content-Encoding SetInputFilter DEFLATE SetOutputFilter DEFLATE Header set Content-Encoding gzip 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? Regards, Dennis - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
