this
discussion with let me know.
I'll report back with my test results. Thanks!
Kyle Harper
From: Christopher Schultz ch...@christopherschultz.net
To: Tomcat Users List users@tomcat.apache.org
Date: 06/18/2012 07:49 PM
Subject:Re: Modify HTTP status returned by stopped context
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kyle,
On 6/19/12 9:26 AM, kharp...@oreillyauto.com wrote:
Where did you configure this? Which webapp's web.xml? In the ROOT
context (/). I'm on Ubuntu 10.04 with defaults, so
/var/lib/tomcat6/webapps/ROOT/WEB-INF/web.xml
Ok.
Yes, the longest
Hello Chris,
No, the webapp is selected first, then the path is trimmed (if
necessary) and then the longest-match wins when matching against
url-patterns configured in that webapp's web.xml.
...
Sorry, longest match wins for URI matching once the webapp has been
selected.
Makes sense. I
*resending this to group, as it has been about 3 hours and isn't showing up
yet on list*
Hello Chris,
No, the webapp is selected first, then the path is trimmed (if
necessary) and then the longest-match wins when matching against
url-patterns configured in that webapp's web.xml.
...
Sorry,
users@tomcat.apache.org
Date: 06/15/2012 05:05 PM
Subject:Re: Modify HTTP status returned by stopped context
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kyle,
On 6/15/12 12:30 PM, kharp...@oreillyauto.com wrote:
I attempted to do what you prescribed but I am running into a snag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kyle,
On 6/18/12 3:52 PM, kharp...@oreillyauto.com wrote:
Thank you for the direction. I created my own servlet which loads
without error. Here is how I've configured it:
Where did you configure this? Which webapp's web.xml?
servlet
.
I'm not sure where to go from here, and would greatly appreciate any ideas
you (or anyone else) have.
Thanks,
Kyle Harper
From: Mark Thomas ma...@apache.org
To: Tomcat Users List users@tomcat.apache.org
Date: 06/14/2012 03:19 PM
Subject:Re: Modify HTTP status returned by stopped
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kyle,
On 6/15/12 12:30 PM, kharp...@oreillyauto.com wrote:
I attempted to do what you prescribed but I am running into a snag
and can't figure out what I've done incorrectly.
I have a context, we'll call it /foo
In my ROOT web application (/)
Hello,
I am running multiple web applications on a tomcat server. When a request
to a context in the stopped state is made, tomcat is returning 404 not
found rather than 503 unavailable. Is it possible to change this
behavior in any way? Obviously I can't just modify _all_ HTTP 404
responses
On 14/06/2012 20:37, kharp...@oreillyauto.com wrote:
Hello,
I am running multiple web applications on a tomcat server. When a request
to a context in the stopped state is made, tomcat is returning 404 not
found rather than 503 unavailable. Is it possible to change this
behavior in any
Mark,
Very slick. I wasn't aware of the longest-matching logic. I'll give this
a whirl and report back.
Thanks,
Kyle Harper
From: Mark Thomas ma...@apache.org
To: Tomcat Users List users@tomcat.apache.org
Date: 06/14/2012 03:19 PM
Subject:Re: Modify HTTP status returned
11 matches
Mail list logo