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=38745>. 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=38745 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2006-02-22 05:05 ------- (In reply to comment #0) > Can anyone confirm this is happening as I stated and whether this behaviour is > correct? Because as I have just shown, this may also cause other issues for > other people somehow. Yes, this is what is happening, and yes this behaviour is not only correct, but required by the servlet spec (see the javadocs for ServletRequest#getServerPort in section 14.2.16 of the spec). If Tomcat used the actual Connector port (i.e. request.getLocalPort), then weird things would start to happen when the Tomcat port is being natted, or Tomcat is behind a proxy. This would be much worse than just trying to handle one buggy client. Of course, since you are on Windows, there is nothing stopping you from simply running Tomcat on the default port 80. Then all of your problems would be solved :). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
