]
Remy Maucherat commented on JBAS-4353:
--------------------------------------
We've run into that issue very recently. There's a directive for that (but the
default value is not right).
JkOptions ForwardURICompatUnparsed
request.getRequestURL/request.getRequestURI return different results
depending on running behind mod_jk or not.
---------------------------------------------------------------------------------------------------------------
Key: JBAS-4353
URL:
http://jira.jboss.com/jira/browse/JBAS-4353
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.2.0.CR2
Reporter: Jon Stevens
Assigned To: Remy Maucherat
Priority: Blocker
Running with the bundled Tomcat on port 8080, i get this:
requestUrl:
http://HOSTNAME:8080/data/xxx/members/4457/pictures/thumbs/Behind%20the%2...
requestUri: /data/xxx/members/4457/pictures/thumbs/Behind%20the%20Scenes/peter.jpg
Running tomcat behind mod_jk, I get this:
requestUrl:
http://HOSTNAME/data/xxx/members/4457/pictures/thumbs/Behind the
Scenes/peter.jpg
requestUri: /data/xxx/members/4457/pictures/thumbs/Behind the Scenes/peter.jpg
This is a blocker because I depend on knowing if the string is urlencoded or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: