https://issues.apache.org/bugzilla/show_bug.cgi?id=53554
--- Comment #2 from Tim Starling <[email protected]> --- (In reply to comment #1) > In RFC 1738, about Uniform Resource Locators (URL) > (http://www.rfc-editor.org/rfc/rfc1738.txt) > > > it is written that : > > >>> > 2.2. URL Character Encoding Issues > > [...] > In addition, octets may be encoded by a character triplet consisting > of the character "%" followed by the two hexadecimal digits (from > "0123456789ABCDEF") which forming the hexadecimal value of the octet. > (The characters "abcdef" may also be used in hexadecimal encodings.) > [...] > > <<< > > > So, I guess that httpd is correct when encoding with lower case. > > > I left the report open, just in case, but I think that it should be marked > as FIXED, WONTFIX. I think the RFC is pretty clear about which encoding is preferred, and it's not the one httpd is using. You seem to be using a very loose definition of "correct". There are two ways of doing it: one is preferred, the other is idiosyncratic and breaks caching. It is a simple change and the patch is attached. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
