You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if I just have a screw loose or what, but invalid locale strings ("en_US" instead of "en-US") or missing the header entirely seems to prevent any locale from being resolved in controllers and elsewhere. Supplying a LocaleContextResolver bean doesn't seem to help. LocaleResolver doesn't seem to be compatible due to version, it looks like.
I think I would have anticipated a null locale, instead of a 500 error, or at least a 400...
AcceptHeaderLocaleContextResolver is indeed too strict about this, and needs to leniently handle invalid Accept-Language headers (just like the Servlet API does). As for the contract, this is a separate (but same-named) LocaleContextResolver SPI for WebFlux which I'm also bringing up to date with #21002 now.
Stephen Imhoff opened SPR-16500 and commented
Spring Boot 2.0.0.M7 with the web-flux starter.
Not sure if I just have a screw loose or what, but invalid locale strings ("en_US" instead of "en-US") or missing the header entirely seems to prevent any locale from being resolved in controllers and elsewhere. Supplying a
LocaleContextResolver
bean doesn't seem to help.LocaleResolver
doesn't seem to be compatible due to version, it looks like.I think I would have anticipated a null locale, instead of a 500 error, or at least a 400...
Affects: 5.0.3
Attachments:
Issue Links:
Referenced from: commits cd8a1bd
The text was updated successfully, but these errors were encountered: