Chris et al.,
Thanks having a careful look at the 500 status thing. I realize that
our application is not using Tomcat in the "usual" manner, and that
this unusual use does not a use case make. So the fact that you're
willing to consider fixing it is much appreciated.
I'll keep looking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 10/18/2011 11:13 AM, Konstantin Kolinko wrote:
> I think it is OK to file a bug report for this issue.
Reported against 7.0 trunk (where it is also reproducible), including
simple test case.
https://issues.apache.org/bugzilla/show_bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
At this point, all discussion is academic because you sound like you
are stuck with what you've got. I would recommend fixing the apparent
bugs in your replacement default servlet, but I don't get to make
requirements decisions on your project
2011/10/18 Nathan Potter :
>
> On Oct 18, 2011, at 6:50 AM, Konstantin Kolinko wrote:
>
>> 2011/10/17 Nathan Potter :
>>>
>>>
>>> Greetings,
>>>
>>> I am new to this list and I apologize in advance if this has been covered
>>> (although searching the archives did not lead me to a related thread):
>
On Oct 18, 2011, at 6:50 AM, Konstantin Kolinko wrote:
2011/10/17 Nathan Potter :
Greetings,
I am new to this list and I apologize in advance if this has been
covered
(although searching the archives did not lead me to a related
thread):
In my web application I need to utilize the JSP
2011/10/17 Nathan Potter :
>
>
> Greetings,
>
> I am new to this list and I apologize in advance if this has been covered
> (although searching the archives did not lead me to a related thread):
>
> In my web application I need to utilize the JSP servlet, but I need to use a
> different servlet map
> From: Nathan Potter [mailto:npot...@opendap.org]
> Subject: Re: JspServlet - Unexpected behavior, possible bug...
> So is the idea to identify to the filter: "These are the things for
> the org.apache.catalina.servlets.DefaultServlet" and then send
> everything
On Oct 17, 2011, at 6:02 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 8:56 PM, Nathan Potter wrote:
I don't see how to do it without using a rewrite rule for every
thing in the top level collection of URL's. I think if you try to
rewrite
On Oct 17, 2011, at 6:02 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 8:56 PM, Nathan Potter wrote:
I don't see how to do it without using a rewrite rule for every
thing in the top level collection of URL's. I think if you try to
rewrite
On Oct 17, 2011, at 7:44 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 10/17/2011 10:11 PM, Caldarale, Charles R wrote:
From: Nathan Potter [mailto:npot...@opendap.org] Subject: Re:
JspServlet - Unexpected behavior, possible bug...
I don't se
On Oct 17, 2011, at 7:11 PM, Caldarale, Charles R wrote:
From: Nathan Potter [mailto:npot...@opendap.org]
Subject: Re: JspServlet - Unexpected behavior, possible bug...
I don't see how to do it without using a rewrite rule for
every thing in the top level collection of URL's.
On Oct 17, 2011, at 6:36 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 9:21 PM, Nathan Potter wrote:
No, but if you assign a servlet to "/" or "/*" it gets call
foreverything before anything starting with "*". Basically starts
with "/" tru
On Oct 17, 2011, at 6:41 PM, Caldarale, Charles R wrote:
From: Nathan Potter [mailto:npot...@opendap.org]
Subject: Re: JspServlet - Unexpected behavior, possible bug...
by default servlet I mean the servlet mapped to "/" or "/*"
And right there is your terminology p
On Oct 17, 2011, at 6:08 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 4:53 PM, Nathan Potter wrote:
On Oct 17, 2011, at 1:07 PM, Christopher Schultz wrote:
I'd be interested to see what else happened. It looks like
JspServlet is trying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 10/17/2011 10:11 PM, Caldarale, Charles R wrote:
>> From: Nathan Potter [mailto:npot...@opendap.org] Subject: Re:
>> JspServlet - Unexpected behavior, possible bug...
>
>> I don't see how to do it without usin
> From: Nathan Potter [mailto:npot...@opendap.org]
> Subject: Re: JspServlet - Unexpected behavior, possible bug...
> I don't see how to do it without using a rewrite rule for
> every thing in the top level collection of URL's.
You only need to have the filter
> From: Nathan Potter [mailto:npot...@opendap.org]
> Subject: Re: JspServlet - Unexpected behavior, possible bug...
> by default servlet I mean the servlet mapped to "/" or "/*"
And right there is your terminology problem. The default servlet is the one
mapp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 9:21 PM, Nathan Potter wrote:
> No, but if you assign a servlet to "/" or "/*" it gets call
> foreverything before anything starting with "*". Basically starts
> with "/" trumps starts with "*" when applying url patterns.
If I'
On Oct 17, 2011, at 6:00 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 4:50 PM, Nathan Potter wrote:
Historically, the servlet that I am working with has been the
default servlet. Tomcat's default servlet was used to serve docs
from a subd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 4:53 PM, Nathan Potter wrote:
> On Oct 17, 2011, at 1:07 PM, Christopher Schultz wrote:
>
>> I'd be interested to see what else happened. It looks like
>> JspServlet is trying to compile the directory. The "file" (the
>> direc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 8:56 PM, Nathan Potter wrote:
> I don't see how to do it without using a rewrite rule for every
> thing in the top level collection of URL's. I think if you try to
> rewrite the root of the context that it's going to disable othe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 4:50 PM, Nathan Potter wrote:
> Historically, the servlet that I am working with has been the
> default servlet. Tomcat's default servlet was used to serve docs
> from a subdirectory of the context dir, and everything else was
>
On Oct 17, 2011, at 5:38 PM, Caldarale, Charles R wrote:
From: Nathan Potter [mailto:npot...@opendap.org]
Subject: Re: JspServlet - Unexpected behavior, possible bug...
A new feature has been added to the web application that requires
JSP. But because an alternative default servlet is
> From: Nathan Potter [mailto:npot...@opendap.org]
> Subject: Re: JspServlet - Unexpected behavior, possible bug...
> A new feature has been added to the web application that requires
> JSP. But because an alternative default servlet is defined, this
> disables the use of the J
On Oct 17, 2011, at 1:07 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 12:47 PM, Nathan Potter wrote:
- BUT, If I request a URL (without a trailing slash) that
references an existing directory within the the JSP servlet's
purview, I get an
Chuck,
I may not NEED to do it. It's just what I figured out to do.
Historically, the servlet that I am working with has been the default
servlet. Tomcat's default servlet was used to serve docs from a
subdirectory of the context dir, and everything else was dynamically
generated by the de
> From: Nathan Potter [mailto:npot...@opendap.org]
> Subject: Re: JspServlet - Unexpected behavior, possible bug...
> Does that mean that you figured out what I was talking about or how to
> correct/adjust the behavior?
No, but hopefully Ms Ramsey will now stop polluting the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan,
On 10/17/2011 12:47 PM, Nathan Potter wrote:
> - BUT, If I request a URL (without a trailing slash) that
> references an existing directory within the the JSP servlet's
> purview, I get an HTTP status 500 (Internal Server Error).
> http://loc
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Subject: Re: JspServlet - Unexpected behavior, possible bug...
> On 10/17/2011 2:29 PM, Ann Ramsey wrote:
> > we figured it out - thank you
> What was the problem?
It appears Ms Ramsey is completely clueless
Honestly, I'm just using another person's login. We don't really have an IT
guy, so I don't understand all the responses. I really appreciate everyone
responding though. You guys are very nice to respond!
Regards,
Ann
On Mon, Oct 17, 2011 at 2:55 PM, Nathan Potter wrote:
>
>
> Does that mean th
Does that mean that you figured out what I was talking about or how to
correct/adjust the behavior?
I'm just curious if I did find a minor issue...
Nathan
On Oct 17, 2011, at 11:29 AM, Ann Ramsey wrote:
we figured it out - thank you
On Mon, Oct 17, 2011 at 1:14 PM, Caldarale, Charle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ann,
On 10/17/2011 2:29 PM, Ann Ramsey wrote:
> we figured it out - thank you
What was the problem? This isn't tech support: this is a community of
volunteers and users. How about helping them out and explaining what
went wrong so others can figure i
we figured it out - thank you
On Mon, Oct 17, 2011 at 1:14 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Nathan Potter [mailto:npot...@opendap.org]
> > Subject: JspServlet - Unexpected behavior, possible bug...
>
> > In my web application I need to utilize the JSP servle
> From: Nathan Potter [mailto:npot...@opendap.org]
> Subject: JspServlet - Unexpected behavior, possible bug...
> In my web application I need to utilize the JSP servlet, but
> I need to use a different servlet mapping:
>
> jsp
> /jsp/*
>
Before going any further,
34 matches
Mail list logo
