Reduce logging severity/don't log expired tokens/401s

Created on 23 September 2019, over 5 years ago
Updated 6 February 2023, about 2 years ago

It's a common pattern for clients to attempt a request with an access token, and if it responds with a 401 HTTP status code, refresh and try again. Currently this module logs these as errors, which is probably log spam in the sense that it's not a very actionable error for administrators on the server-side.

Generating proper response codes is handled in #2840205: Error messages/codes should be more helpful & match spec. β†’ - this issue is for the logging component.

πŸ“Œ Task
Status

Needs review

Version

5.2

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States bradjones1 Digital Nomad Life

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024