-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 4/18/14, 3:37 PM, David Wall wrote:
> Thanks, Christopher.
>
> One last question has to do with the filter-mapping's url-pattern
> element.
>
> Are /* and *
> the same?
>
> My impression is that /* is more correct since a * pattern impl
Thanks, Christopher.
One last question has to do with the filter-mapping's url-pattern element.
Are /* and * the
same?
My impression is that /* is more correct since a * pattern implies a
file name suffix but there's nothing after it. Is that true, or do /*
and * work the same to mean to m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 4/18/14, 2:57 PM, David Wall wrote:
>
> On 4/17/2014 7:50 AM, Christopher Schultz wrote:
>> I'll take a look at the code to see if maybe we can conditionally
>> log something somewhere when we get a 400 error. You can probably
>> get info
On 4/17/2014 7:50 AM, Christopher Schultz wrote:
I'll take a look at the code to see if maybe we can conditionally log
something somewhere when we get a 400 error. You can probably get
information about it by enabling DEBUG logging on the component that
throws the 400 error, but you'll likely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 4/16/14, 7:54 PM, David Wall wrote:
>
> On 4/16/2014 3:17 PM, Christopher Schultz wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>>
>> The access log of course does not give the whole story. It's
>> possible that the clien
I've never done a request dumper before, but is there a way to trigger
it only if Tomcat is going to issue a 400?
Sorry for replying to my own posting, but for JSP urls, we do seem to
know that request.getScheme() for example returns null when things are
bad, though I'm not sure how a bad re
On 4/16/2014 3:17 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The access log of course does not give the whole story. It's possible
that the client sent for example a badly-formed HTTP header value. In
those cases, the request-line (shown in the access log) c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David,
On 4/16/14, 12:42 PM, David Wall wrote:
> I am running Tomcat 7.0.47 and it occasionally returns HTTP status
> codes of 400, such as the following from my access log.
>
> A 400 suggests a malformed request, but many of these are simple
> GET
I am running Tomcat 7.0.47 and it occasionally returns HTTP status codes
of 400, such as the following from my access log.
A 400 suggests a malformed request, but many of these are simple GET
requests on an image, so it seems odd they are malformed. We're not
positive, but it seems that as th
