DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2003-07-31 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2003-07-31 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log --- Additional Comments From [EMAIL PROTECTED] 2003-08-01 00:32 --- Remy: the servlet javadoc has the following for getServerPort(): Returns the port number on which this request was received. For

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2003-05-31 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log --- Additional Comments From [EMAIL PROTECTED] 2003-05-30 19:38 --- getServerName and getServerPort come from the Host header. Virtual hosting basics. For security, you should be using isSecure, getRemoteUser/Pri

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2003-05-31 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log --- Additional Comments From [EMAIL PROTECTED] 2003-05-30 18:56 --- It seems that the getServerPort() method returns the port as specified in the Host header of the received message, not the port of the con

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2003-04-04 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2003-02-14 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log --- Additional Comments From [EMAIL PROTECTED] 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: Star

getServerPort

2003-01-28 Thread Doug Davis
Just wondering if anyone knows about the status of: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13172 I'm using Tomcat 4.1.18 and getServerPort seems to still only return 80 even though its running on port 8080. thanks, -Dug -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECT

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2002-10-01 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|RE

DO NOT REPLY [Bug 13172] - Port incorrect in getServerPort and in access log

2002-10-01 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 13172] New: - Port incorrect in getServerPort and in access log

2002-10-01 Thread bugzilla
gzilla/show_bug.cgi?id=13172 Port incorrect in getServerPort and in access log Summary: Port incorrect in getServerPort and in access log Product: Tomcat 4 Version: Unknown Platform: Sun OS/Version: Solaris Status: NEW Severity: