Stack trace for uncaught exception?
cantor.2 at osu.edu
Mon Dec 28 18:30:31 UTC 2020
(And obviously, it should just log and ignore an invalid header in that area.)
On 12/28/20, 1:29 PM, "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:
On 12/28/20, 12:22 PM, "users on behalf of Christopher Bongaarts via users" <users-bounces at shibboleth.net on behalf of users at shibboleth.net> wrote:
> The errors in question are coming from the embedded browser in the 4D database client (user agent:
Seems to be a lot of that.
> This was working on our previous IdP (3.3.0, Jetty 9.3.something, RHEL7-provided Oracle JDK 8).
I assume the old code may have manually parsed those headers and not been correctly coded. We use Java's API to do it now, it just does what it does and those are invalid, so it rejects them.
But I assume somebody must have filed a bug on this somewhere? If it's being uncaught, that's a bug. I'd suggest filing it to make sure we get to it.
> Is there a way to get the stack trace logged when an uncaught exception occurs?
Well, I would have thought that it was simply passing the underlying exception to logback. The code is supposed to do that, and then it would be up to the stack trace setting in the logback format string, which we have set to full I think.
For Consortium Member technical support, see https://urldefense.com/v3/__https://wiki.shibboleth.net/confluence/x/coFAAg__;!!KGKeukY!iRvZOdj-pXCGUJpfz6cNkwk1sk10CJ--1SNO6I_rhY_SnD9Kxjdxg73psAaQVIQ$
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users