-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reduce JWT error logging in WebSockets #303
Comments
lukaskabc
added a commit
to lukaskabc/termit
that referenced
this issue
Nov 30, 2024
…nd match log level with HTTP authentication exception logging
lukaskabc
added a commit
to lukaskabc/termit
that referenced
this issue
Nov 30, 2024
…ception handling
lukaskabc
added a commit
to lukaskabc/termit
that referenced
this issue
Dec 8, 2024
…e methods and additionally check exception based on annotation value
ledsoft
pushed a commit
that referenced
this issue
Dec 8, 2024
…log level with HTTP authentication exception logging
ledsoft
pushed a commit
that referenced
this issue
Dec 8, 2024
ledsoft
pushed a commit
that referenced
this issue
Dec 8, 2024
… and additionally check exception based on annotation value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, WebSocket connectors pollute the log with repeated exceptions regarding expired JWTs. This is quite annoying as it is difficult to navigate the log to get to relevant information.
The following exception repeats in the log:
The text was updated successfully, but these errors were encountered: