-
Notifications
You must be signed in to change notification settings - Fork 40
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
[feature request] Internal server error triggered by “Accept-Charset” header with unexpected value #300
Comments
Could you ask for the stacktrace so that we don't have to run the samples for ourselves? As long as the unexpected header doesn't cause a server side crash - this would likely to be quite a minor issue. |
If we are leaking a stack trace to the client this can be a serious security issue |
Yes, this is a bug but only a minor issue. Here's a stack trace (though, wrapped with another exception to understand how that exception can be triggered):
|
A simple but lazy fix would be to reject/ignore A more involved and potentially performance-impacting fix would be to make sure to not assume that we have a |
Seems low priority to me. Failing to process the request due to the bad charset value is not too bad. But ignoring the exception and proceeding as if no charset was provided looks like a good solution. |
https://www.rfc-editor.org/rfc/rfc9110.html#field.accept-charset even mentions |
Picked from: https://discuss.lightbend.com/t/internal-server-error-triggered-by-accept-charset-header-with-unexpected-value/10427
Which expects the header to be ignored.
The text was updated successfully, but these errors were encountered: