Closed
Description
Juergen Hoeller opened SPR-15426 and commented
As pointed out against #18884, AcceptHeaderLocaleResolver's default locale currently only kicks in if no Accept-Language header has been specified. It should also kick in if no supported locale is found in a given header, aligning with #17915.
Affects: 4.3.7
Issue Links:
- Flexible locale resolution based on supported languages [SPR-13330] #17915 Flexible locale resolution based on supported languages
- AcceptHeaderLocaleResolver should allow to define a default Locale [SPR-14312] #18884 AcceptHeaderLocaleResolver should allow to define a default Locale
- Invalid/missing locale strings in header prevents resolving the locale [SPR-16500] #21043 Invalid/missing locale strings in header prevents resolving the locale
- AcceptHeaderLocaleResolver should match country locales against supported language locales [SPR-16457] #21002 AcceptHeaderLocaleResolver should match country locales against supported language locales
- Make SessionLocaleResolver's attribute name configurable [SPR-15450] #20011 Make SessionLocaleResolver's attribute name configurable