On Fri, 1 Feb 2019 at 13:30, Maxim Dounin wrote:
Hi Maxim!
The 406 looks wrong to me. It tells the client that the response
> is not acceptable as per accept headers in the request. In your
> case it is more like 500,
Concur. I did some research on Wikipedia and followed Cloudflare's exampl
Hello All!
I'm running a reverse proxy and I want to trap when upstream is sending me:
Content-Encoding: gzip
...and on those occasions return (probably) 406 downstream to the client;
the reason for this is that I am always using:
proxy_set_header Accept-Encoding "identity";
...so the upst
Hi Francis!
On 18 December 2017 at 22:26, Francis Daly wrote:
>
> You do currently have a header_filter_by_lua_block{} section, where you
> appear to rewrite three specific content-security-related headers based
> on multiple regex matches.
>
> Could you not do exactly the same with the "Location
Hi! I am using Nginx 1.12.2 in a large and complex reverse-proxy
configuration, with lots of content-rewriting (subs_filter, lua, ...).
Problem:
- the client connects to my proxy
- my proxy forwards the request to the origin
- the origin responds with a 302:
"Location: http://www.foo.com/"; ...
