Define charset by default in SAML POST views

[Cantor, Scott]

On 12/15/14, 7:48 PM, "Marvin Addison" <marvin.addison at gmail.com> wrote:
>
>Ok. I don't think there's much of a use case for changing the encoding, 
>so I'll go that route. You can always edit the profile-specific template, 
>so it's still liable to change.

Ok.

>In my experience it's best to declare the encoding everywhere you can. We 
>ran into an issue with non-Latin characters not rendering properly in one 
>of our Java webapps, and found that specifying the encoding in the HTML 
>header was one of a few places you had to declare encoding to get the 
>characters to render properly.

Right, I'm sure that was the reasoning. Note that the SAML templates are 
basically pushing base64 or URL-encoded data around, so it's 7-bit ASCII, 
and basically immune to the problems.

-- Scott