Logging for an HTTP client bean

[Wessel, Keith]

Thanks, Brent.

I see no mentions of org.apache.http or its child classes anywhere else in my logback config. So, I don’t think that’s it.

And I know the config is getting reloaded because my change is to a Docker container running locally that I’m rebuilding and redeploying after making the change.

Oddly, I don’t think I’m even seeing debug logs for other pieces using an HTTP client such as the metadata providers. They all use org.apache.http and should be generating some noise if that’s turned up to debug, correct?

Keith


From: users <users-bounces at shibboleth.net> On Behalf Of Brent Putman via users
Sent: Friday, December 8, 2023 8:49 PM
To: users at shibboleth.net
Cc: Brent Putman <putmanb at georgetown.edu>
Subject: Re: Logging for an HTTP client bean



On 12/8/23 5:36 PM, Wessel, Keith via users wrote:
Thanks, Brent. Sorry, I meant to state that this is still the latest of V4. We’re planning to do our V5 upgrade during the holiday break.

Any guidance on V4?

Keith




Hmm, ok.  org.apache.http is the correct package name for the top-level package.  Are you sure there isn't another entry in your logback config for a more specific package like org.apache.http.client that is on a more restrictive logging level and is therefore overriding what you are adding?

Other than that, I can only suggest that something about what you are doing isn't correct - like you are editing the wrong logback file, or you don't have the logback auto load thing enabled and so need to restart the IdP, etc.

Maybe someone else can think of something I'm missing.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20231211/9bacb605/attachment.htm>