On 21/02/2019 13:50, Matthias Müller wrote:
>
> (2) How do I enable transparent compression, i.e. mask [1] from the
> proxied request so that the application server never attempts response
> compression and always lets NGINX perform that task?
Try
proxy_set_header Accept-Encoding "";
--
Arka
Hi
was there any solution for this issue?
thanks a lot
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,259748,283116#msg-283116
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello all I have a server usin Debian 9.3. I have migrated from Lighttpd to
ngings to be able to use its reverse proxi capabilities to use OpenHab
my default file is:
"
server {
listen80;
server_name 192.168.1.246;
error_l
When running NGINX as a reverse proxy (e.g. in front of an application
server) I know how to switch on gzip/deflate from the documentation.
What I am looking for is a *transparent* compression by NGINX, i.e. the
proxied application server should be unaware that the original client
request was aski
Assume, you have a really slow client.
Nginx will get upstream response in milliseconds and will start feeding
data to a client
In 3 seconds nginx completed the transfer and issues a log entry.
And you see what you see.
If this issue involves a single client - most likely it's a client issue
(
Jon,
You need to find out what is “true”. From the perspective of nginx,
this post request took 3.02 secs - but where was the time actually spent?
Do you have root access on both your nginx host and your upstream host
that is behind your elastic load balancer? If so, you can run a filtered
tcpdu
