java - ESAPI canonicalize malforming url -


We have an application that accepts URLs from users. This data requires verification, and we are using ESAPI for this purpose. However, we are struggling with empursed URLs.

The problem arises when ESAPI can access data before verification. URL & amp; pid = 123 for example Ï ?? D = 123. since I?? Not whitelisted, verification fails

I have tried to encode it, but ESAPI is more cunning than that and canonicalization to avoid double encoding and mixed encoding. I'm a little stumped here and I'm not sure how to move forward.

This problem is in ESAPI. I started working on solving it, but since I know It is not that when a patch will happen, I can only send you references to the a action in your comments in OP where I had linked the same answer, to parse / break the URL By using java.net.URI and javax.ws.rs.core.Uribuilder , you can cancel the piece, and after that Can rebuild Uarel. I will redirect the link OP has given the example I gave after changing the topics of the middle question, its question is on the second half.

Comments

Popular posts from this blog

Java - Error: no suitable method found for add(int, java.lang.String) -

java - JPA TypedQuery: Parameter value element did not match expected type -

c++ - static template member variable has internal linkage but is not defined -