Shibboleth, Tomcat, AJP and UTF-8 conversion
Mark Juszczec
mark.juszczec at gmail.com
Thu Oct 20 12:40:51 EDT 2016
On Thu, Oct 20, 2016 at 10:36 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> > The data bytes are percolating thru Tomcat correctly (I've verified
> them) until
> > they get handled by ByteChunk and converted to a String.
>
> If you found the code doing it, then I guess it should be evident whether
> that conversion is happening conditionally based on any settings or not,
> but if not, I don't know why people have claimed the connector encoding
> changes things.
>
>
At debug time I've set breakpoints on the methods that would have to be
called to change the encoding and NONE of these breakpoints are being hit.
> You found what seems to be a community-offered workaround for doing a
> conversion of the data back into UTF-8, and so obviously the thing to do is
> to try it. You seemed to be unsure whether that trick would work, but since
> the trick is about doing something to a String, it doesn't depend on where
> the String came from. getHeader, getAttribute, doesn't matter. Same
> difference. If the data is encoded in ISO-whatever, the trick will work.
>
>
My hesitancy is that other research has designated this as unreliable and
unnecessary if you have configured encoding properly in Apache and Tomcat
and all the other things that may touch your incoming data.
I'm slowly reconciling myself to the fact that, in other cases it could be
unreliable and unnecessary, but in THIS particular use case its the only
way to go.
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161020/e5e111c5/attachment.html>
More information about the users
mailing list