Hello,

I'm noticing an issue where the square bracket characters are not url encoded when passing to the upstream server. My config is

upstream avatar {
server localhost:8879;
}

location /avatar-internal/ {
internal;
proxy_pass http://avatar/;
}

I'm passing a url encoded value in the X-Accel-Redirect header,
e.g. /avatar-internal/file%5D.jpg?x=1

but nginx sends the url
file].jpg?x=1

instead of the correct
file%5D.jpg?x=1

It does not re-encode [ and ] characters. But it seems to re-encode other special characters like ? and #. I'm using version 1.9.4. This seems like a bug.



Edited 1 time(s). Last edit at 01/06/2016 06:53PM by isuraed.

Another inconsistency I see is if I pass an unescaped URL in the header, then special characters are escaped EXCEPT for square brackets.