IDPv3 internationalization via links and cookies

[Cantor, Scott]

On 11/4/15, 12:48 PM, "users on behalf of Brent Putman" <users-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:



>You probably know better than I what the behavior of SWF is here.  But IIRC, the locale param doesn't need to persist across requests here.  It just needs to be there once, on the initial inbound request, so it is seen by that handler interceptor impl.  That
> "permanently" changes the locale in effect (by calling the setLocale(...) method on the LocaleResolver).  Once it processes it, the param can go away.

Oh, ok. I thought it was one of those things like JSESSIONID where it had to be on every URL.

>I think the intent of the above MVC handler interceptor methodology is to make the locale update "signal" independent of the underlying locale strategy used. For example, they also have a Java Session-based LocaleResolver, which I believe would work transparently with the locale handler interceptor.

I didn't realize it was stateful. The cookie or request header cases obviously would be there on every request, so I assumed the mechanism relied on that.

-- Scott