Hi Markus,
from your previous emails I understood a different picture, namely that you
didn't want to send compressed requests to the backend to keep it as simple
as possible.
To solve your problem you might try to use SetOutputFilter INFLATE inside a
dedicated https://httpd.apache.org/docs/2.4/m
have you tried not doing anything in the reverse proxy?
Reverse proxies are supposed to be very "transparent" so every client
request should reach the backend untouched (except for needed headers) and
reply from backend must be delivered to client untouched, let them both
server and client handle
I am not sure exactly how I can configure that, i.e. when I used the
following:
RequestHeader set Accept-Encoding gzip
SetOutputFilter INFLATE
SetOutputFilter DEFLATE
How would Apache know that the content when going to the backend shall be
compressed while the content provided
Hi Markus,
2017-04-26 12:21 GMT+02:00 Markus Gausling :
> Hello,
>
> I am using Apache (2.4.10) as an HTTP Proxy with two virtual hosts
> listening
> on different ports:
> - Forward Proxy
> - Reverse Proxy
>
> Depending on the use case applications either use the Forward Proxy or the
> Reverse Pr
Hello,
I am using Apache (2.4.10) as an HTTP Proxy with two virtual hosts
listening
on different ports:
- Forward Proxy
- Reverse Proxy
Depending on the use case applications either use the Forward Proxy or the
Reverse Proxy.
Now I want to make sure that for both virtual hosts the proxy does han
