You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/12/21 23:07:00 UTC
DO NOT REPLY [Bug 25681] New: -
HTTP request params lost when sent with a URL ending with a folder w/o '/' at the end of URL
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25681>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25681
HTTP request params lost when sent with a URL ending with a folder w/o '/' at the end of URL
Summary: HTTP request params lost when sent with a URL ending
with a folder w/o '/' at the end of URL
Product: Tomcat 5
Version: 5.0.16
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Critical
Priority: Other
Component: Servlet & JSP API
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: sabiq@purdue.edu
CC: sabiq@purdue.edu
Given a URL like:
http://www.ultranet.tv/site/web_hosting?l=tr
the request logged in J2EE 1.4 DR (Tomcat 5) is:
64.219.140.49 - - [21/Dec/2003:15:43:05 -0600] "GET /site/web_hosting/
HTTP/1.1" 200 7912
This apparently means that the request parameters have been lost while
resolving the URL.
If the request URL is modifed to http://www.ultranet.tv/site/web_hosting/?
l=tr, the log shows:
64.219.140.49 - - [21/Dec/2003:15:36:35 -0600] "GET /site/web_hosting/?l=tr
HTTP /1.1" 200 7842
Thus, the request parameters are apparently preserved.
Unless the HTTP standards dictate that the request params in the first request
should be lost, which i can't imagine to be the case, this is a bug.
P.S. In J2EE 1.4 Beta 2, the first request gets logged as follows:
64.219.140.49 - - [21/Dec/2003:15:47:00 -0600] "GET /site/web_hosting?l=tr
HTTP/1.1" 302 -
64.219.140.49 - - [21/Dec/2003:15:47:00 -0600] "GET /site/web_hosting/?l=tr
HTTP/1.1" 302 -
64.219.140.49 - - [21/Dec/2003:15:47:03 -
0600] "GET /site/web_hosting/index.jsp?l=tr HTTP/1.1" 200 7842
P.P.S. It appears that there has been an attempt to make processing of these
URLs more efficient by avoiding 302 responses, and resolving to the final
location internally. However, this bug was introduced in doing so. The fix is
likely to be trivial for someone who is familiar with Tomcat architecture.
Thanks,
rs.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org