Forum: NGINX Proposed Patch - url encoding all upper case...

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
87d08bdf14ef944738d2a81105b12606?d=identicon&s=25 Brian Moran (Guest)
on 2009-05-12 01:12
(Received via mailing list)
I'd like to propose that URI encoding be done using upper case
characters instead of lower case characters. Both seem to be acceptable;
I'm only requesting this since most of the other libraries that we use
that do URI encoding use upper case characters.

nginx 0.7.6 src/core/ngx_string.c

diff ngx_string.c~ ngx_string.c
1096c1096
<     static u_char   hex[] = "0123456789abcdef";
---
 >     static u_char   hex[] = "0123456789ABCDEF";
2974d09ac2541e892966b762aad84943?d=identicon&s=25 "坏人" (Guest)
on 2009-05-12 22:43
(Received via mailing list)
可以改代码编译后直接使用;也可以用内嵌的perl灵活设置,效率也非常高

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,1918,1920#msg-1920
87d08bdf14ef944738d2a81105b12606?d=identicon&s=25 Brian Moran (Guest)
on 2009-05-13 01:27
(Received via mailing list)
坏人 wrote:
> 
可以改代码编译后直接使用;也可以用内嵌的perl灵活设置,效率也非常高
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,1918,1920#msg-1920
>
>
>
The reason that I'm asking for the change in NGINX is that in one
particular application (X-Accel-Redirect to AWS S3), calculation of a
server variable is done on URL encodings done with UPPER CASE
characters.

We supply NON-URL encoded URLs to X-Accel-Redirect - these are
re-encoded by nginx using lower case characters for any hex values, and
consequently the server variable calculation (already done before
X-Accel-Redirect) fails.
2974d09ac2541e892966b762aad84943?d=identicon&s=25 Alex Andrienko (Guest)
on 2011-10-28 14:30
(Received via mailing list)
Please excuse me for the necroposting, but what's the decision for the
proposed patch?
My Nginx reverse proxy malfunctions due to this problem.(
Is there any workaround for the problem?

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,1918,217439#msg-217439
This topic is locked and can not be replied to.