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=27705>. 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=27705 HttpServletResponse.encodeURL does not work correctly with https [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2004-03-19 14:31 ------- I'm sorry but I do not agree. The spec states: [quote] A web application is rooted at a specific path within a web server. For example, a catalog application could be located at http://www.mycorp.com/ catalog. All requests that start with this prefix will be routed to the ServletContext which represents the catalog application. [/quote] It does not say: Any prefix that is different will/shall/must be routed to a different web application. It unfortunately does not state either: There may be many prefixes pointing to the same web application, depending on the configuration of the web server. ..and this is my point: The spec is ambiguous. The programmers should look at the problem and not at an ambigous spec and resolve the ambiguity by coding resrictivly. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
