On 28 Nov 2023, at 09:41, Mark Thomas <ma...@apache.org> wrote:
>> What do I need to do to see the exception that generated the bad request, so
>> that I know specifically what’s wrong and can fix it?
>
> Enabling debug logging for
>
> org.apache.coyote.http11.Http11Processor may help.
>
> It is probably the tightening up of the HTTP parsing that is triggering the
> 400 response.
I eventually attached a remote debugger and stopped on all exceptions to get
it. A problem with unmarshalling was being triggered then replaced with a
generic 400. We’re now stuck on another bug, same symprom, this time a 500 with
no exception.
What I’m finding is that the following valve on v9.0.65 has no effect:
<Valve className="org.apache.catalina.valves.ErrorReportValve"
showReport="true"
showServerInfo="true" />
Instead of rendering the exception in the output, we get the following:
<!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server
Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;}
h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2
{font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;}
.line
{height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP
Status 500 – Internal Server Error</h1><hr class="line" /><p><b>Type</b> Status
Report</p><p><b>Message</b> Internal Server Error</p><p><b>Description</b> The
server encountered an unexpected condition that prevented it from fulfilling
the request.</p><hr class="line" /><h3>Apache Tomcat/9.0.65</h3></body></html>
Is this a known problem?
Regards,
Graham
—
