https://bz.apache.org/bugzilla/show_bug.cgi?id=62459
--- Comment #4 from Guido Jäkel <g.jae...@dnb.de> --- (In reply to Mark Thomas from comment #3) > Can you please provide an example of a URI presented by a client that > demonstrates this issue. Dear Mark, A real world example is http://nbn-resolving.org/urn:nbn:de:gbv:7-11858%2F00-1735-0000-0001-B8C0-F-4 , it will answer with a redirect to http://ediss.uni-goettingen.de/handle/11858/00-1735-0000-0001-B8C0-F Without the patch, this will forwarded as /urn:nbn:de:gbv:7-11858%252F00-1735-0000-0001-B8C0-F-4 This example is taken from real production which uses "JkOptions +ForwardURICompatUnparsed" at the moment as a workaround. But with the suggested patch (as proved in our test stage), one may use "+ForwardURIProxy", again. In addition, you have to use "AllowEncodedSlashes NoDecode" in the corresponding VHost, too. I was not able to use this as a global option, this seems to be another issue. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
