[JIRA] Commented: (JOST-184) It would be nice if ESAPI.encodeForURL could be made to work
coding@idp.protectnetwork.org (JIRA)
noreply at shibboleth.net
Thu Aug 16 11:56:06 EDT 2012
[ https://issues.shibboleth.net/jira/browse/JOST-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14331#comment-14331 ]
coding at idp.protectnetwork.org commented on JOST-184:
----------------------------------------------------
Thanks for looking into those alternatives and doing that research. I can see that I do indeed have a lot of options here. I will attempt to call the default after bootstrap and report back!
> It would be nice if ESAPI.encodeForURL could be made to work
> ------------------------------------------------------------
>
> Key: JOST-184
> URL: https://issues.shibboleth.net/jira/browse/JOST-184
> Project: OpenSAML 2 - Java
> Issue Type: Improvement
> Components: Security
> Affects Versions: 2.5.3
> Reporter: Rod Widdowson
> Assignee: Chad La Joie
> Priority: Trivial
> Fix For: 2.5.4
>
> Time Spent: 15 minutes
> Remaining Estimate: 0 minutes
>
> I have just "borrowed" esapi from OpenSAML to do nearly all the escaping for the DS jsp page. I appreciate that this very much stretches the bounds of what it was initially intended for and is a bit of 'creature feep'...
> I couldn't use encodeForURL because it throws a nested exception. The root cause is that ESAPI.securityConfiguration().getCharacterEncoding() (line 400 of org.owasp.esapi.reference.DefaultEncoder) returns null. This in turn throws an exception in the error handling but we needn't worry about that.
> I took a _very_ brief look at the esapi security configuration and it looked to be hard wired (which feels like what it should be). So, might it be possible to add "utf-8" as a CharacterEncoding (assuming that it makes sense for the entire stack).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the commits
mailing list