-
Notifications
You must be signed in to change notification settings - Fork 73
OCPBUGS-115307: bugfix: default to english when Accept-Language header contains more than 1000 underscores #253
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
Merged
openshift-merge-bot
merged 1 commit into
openshift:master
from
everettraven:bugfix/accept-language-header-underscore-limit
Sep 3, 2026
+30
−0
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test passes even without the new guard;
ParseAcceptLanguage()would return an error because the value isn't a valid language. I understand that the test now passes because of the new guard, but I'm worried about regressions if e.g. we break the guard accidentally.However, to be honest, I don't know whether it's possible to write a test that will help prevent such regressions, because the function's output doesn't help distinguish the cases (unless we capture and check the logged error somehow).
Therefore I won't block the PR on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, without a refactor here such that the function actually returns an error case I'm not sure there is a way to reliably prove that we are testing the exact path we are intending other than making sure we are getting our fallback language.
In order to properly test this here, we would have to construct a language header with >1000 language tags separated by
_and I'm not sure that is actually possible without significantly more work (I don't think go is aware of that many language tags).I'm not sure the additional verification is worth the squeeze here but 🤷