Stages: if no preferred locales are specified, use the default locales #100
Conversation
This file contains 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
… (e.g. OpenAM's), followed by the JVM's default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If no preferred locales are specified (e.g. not as a query parameter & not in the Accept-Language header), use the default locales.
This means the app's (e.g. OpenAM's), followed by the JVM's default.
This will allow OpenAM to comply with the documented behaviour for OpenAM 13.
Specifically, this allows the RESTful user self-service APIs to work without crashing due to "java.lang.IllegalArgumentException: Cannot find suitable translation from given choices" if no locale is specified.