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/02/14 19:16:47 UTC
DO NOT REPLY [Bug 13172] -
Port incorrect in getServerPort and in access log
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=13172>.
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=13172
Port incorrect in getServerPort and in access log
------- Additional Comments From ser@germane-software.com 2003-02-14 18:16 -------
I'm seeing this bug in Tomcat 4.1.(12|18):
...
Feb 12, 2003 4:23:58 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on port 8080
Feb 12, 2003 4:23:58 PM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on tcp port 8009
...
AuthType: null
ContextPath: /formstk
Method: GET
PathInfo: null
PathTranslated: null
QueryString: null
RequestURI: /formstk/query
RequestURL: http://localhost/formstk/query
ServletPath: /query
Protocol: HTTP/1.0
ServerName: localhost
Scheme: http
ServerPort: 80
...
This is from a tiny servlet that just dumps some of the HttpServletRequest.get* methods. Jetty
reports the correct values.
I would expect this to be a fairly severe bug; it's enough to bring /our/ project to a grinding
halt.
This occurs in:
jakarta-tomcat-4.1.12-LE-jdk14
jakarta-tomcat-4.1.18
java version "1.4.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_01-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.0_01-b03, mixed mode)
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org