Shibboleth Developers

[Chad La Joie <>]

Like damn near everything else with websites, the answer is "it
depends".  There are certainly innumerable site-based solution out
there.  There are also a fair number of sites that do use the browser
settings, sometimes in conjunction with site-based override mechanism.
 Note that site-based UIs only work reliably if you can guarantee that
all information is translated into either all support languages or at
a minimum to a default language.

I personally feel like you do, the client has a mechanism for
specifying language preference and that should be what is used.

On Wed, Jun 15, 2011 at 10:08, Cantor, Scott E. 
<>
 wrote:
> On 6/15/11 9:09 AM, "Chad La Joie" 
> <>
>  wrote:
>>I think having the JSON producer do this makes the most sense.  As you
>>mentioned, you can't get access to the language preferences via
>>Javascript, but the JSON producer will see them when the request comes
>>in.  In most cases this is a list and so the producer could do
>>intelligent things like filter out all but the most preferred in any
>>given choice which is really what you'd want it to do.
>
> As I understand it, nobody uses those headers and when people work on
> language support in web sites, it's all done with custom preferences. I
> base that on the fact that people keep asking to add language indicators
> into SAML despite the fact that both the SP and IdP should be seeing the
> same language headers from the client.
>
> Of course, the JSON feed could do something with custom cookies just as
> easily, but I find the idea detestable when there's a perfectly good UI
> right there in the client.
>
> -- Scott
>
>



-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered