{"id":4157,"date":"2016-05-18T00:00:22","date_gmt":"2016-05-18T00:00:22","guid":{"rendered":"http:\/\/www.garysieling.com\/blog\/?p=4157"},"modified":"2016-05-18T00:00:22","modified_gmt":"2016-05-18T00:00:22","slug":"jersey-container-request-getlanguage-returns-null","status":"publish","type":"post","link":"https:\/\/www.garysieling.com\/blog\/jersey-container-request-getlanguage-returns-null\/","title":{"rendered":"Jersey Container Request: why getLanguage returns null"},"content":{"rendered":"

In Jersey, ContainerRequestContext and ContainerRequest will return null for “getLanguage” when you might expect them to work. For instance, you may see that “getLocale” on ServletRequest gives you a valid value. <\/p>\n

This problem happens because Jersey is pulling “Content-Language”, when what you want is “Accept-Language”. To get the correct value, you need to use “request.getAcceptableLanguages().get(0)”. Note that you could get multiple values (one per language requested). <\/p>\n

The Jersey documentation helpfully describes this method as “the language of the entity or null if not specified”, which is correct, but a little unexpected, since this is actually the language of the response, and not the request.<\/p>\n

\norg.glassfish.jersey.server.ContainerRequest\n<\/pre>\n","protected":false},"excerpt":{"rendered":"
Understanding an unexpected Jersey behavior<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[9],"tags":[300,308,465],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t