Our Tomcat team has been struggling with this issue for a few days:
If a request comes in for https://foo.com/bar.html, which doesn't exist, then a 404 is returned, and we see a standard Tomcat 404 page.
But if a request comes in for https://foo.com/bar.jsp, which also doesn't exist, then our webapp takes control, and returns a 200 with a redirect to a "you are not signed on" page.
In the most recent attempt to correct this, they now return a 404 page of their own design for both of the above scenarios. Unfortunately, if the webapp context we're trying to reach is installed as something other than ROOT (i.e., if we call it "baz," then https://foo.com/baz), then even a correct URL still returns a 404 page.
Seems to me that there's something wrong with this picture. Seems to me that a request for a nonexistent "bar.jsp" should behave the same as one for a nonexistent "bar.html."
Is there something I can pass along to the Tomcat team? -- JHHL --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
