On 17 June 2014 07:49, gwilym <nginx-forum@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 fix for you I'm afraid! However, as a way to get
out of your chicken-and-egg upgrade problem, could you pass a static
header containing the nginx version to your backend, and get it to
switch its X-Accel-Redirect response based on this value?

J

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx