cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16537] - [PATCH] fixed redirect under JRun 3.1
Date Wed, 10 Nov 2004 14:20:26 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=16537>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=16537

[PATCH] fixed redirect under JRun 3.1





------- Additional Comments From durdina@asset.sk  2004-11-10 14:20 -------
I investigated similar/same behaviour on Webshpere 5.1. I prepared a patch (not 
yet subitted), but more complex solution is required.

Take look at attached patch release_2_1_5_1.patch_3.txt:
...
IBM WAS 5.1 doesn't correctly handle redirects to relative urls
i.e. httpResponse.sendRedirect("portal.html"); at current uri 
http:/host/context/myportal/login.html
- GET http:/host/context/myportal/portal.html (Tomcat 4.1)
- GET http:/host/context/portal.html (IBM WAS 5.1)
Absolute redirecting should probably go to http environment layer as a 
configurable feature (web.xml) in the future
...

I suggest to implement minimalistic test sample, that would test:
1.) relative redirect
2.) redirect to url using '..' notation
3.) implement feature "force absolute redirecting" in 
o.a.c.environment.http.HTTPRequest

I can provide testing for WebSphere 5.1, JRun 3.1 and JRun 4.

WDYT?

Mime
View raw message