https://issues.apache.org/bugzilla/show_bug.cgi?id=53469
--- Comment #15 from papegaaij <emond.papega...@topicus.nl> --- Ok, things are getting more clear to me now. Isn't it better to assume that relative URLs always fall within the webapplication? The worst thing that could happen, is that a jsessionid gets appended where it was not needed, which I think is better than leave it out in cases where it should have been appended. The specification is not clear at this point. For sendRedirect it is: "If the location is relative without a leading '/' the container interprets it as relative to the current request URI.". The absence of such a statement in the documentation of encodeURL indicates to me that it is not safe to make the assumption that relative URLs passed to encodeURL are relative to the current request. I think Tomcat should do the best it can without assuming anything that's not backed up by the documentation, even if it means that the outcome may be less than perfect. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
