Jonathan Matthews Wrote:
---
On 17 June 2014 07:49, gwilym nginx-fo...@nginx.us wrote:
The workaround is to _double_ encode so as to send back
image%2520with%2520spaces.jpg to Nginx but we can't roll this out
until
Nginx 1.6 because it
We are updating Nginx from 1.4.7 and 1.6.0 and noticed an error in our app
likely related to the 1.5.9 change: now nginx expects escaped URIs in
X-Accel-Redirect headers.
We have an internal location for proxying content from a backend HTTP system
(Swift, actually). The location block looks like
On 17 June 2014 07:49, gwilym nginx-fo...@nginx.us wrote:
The workaround is to _double_ encode so as to send back
image%2520with%2520spaces.jpg to Nginx but we can't roll this out until
Nginx 1.6 because it breaks 1.4... but we can't roll out 1.6 until the code
is there.
I don't have a nice
