Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: java.net.URI.normalize() problem

Subject: Re: java.net.URI.normalize() problem
Date: Fri, 18 Feb 2005 11:19:37 -0800 (PST)

--- Felipe Moreno <fmoreno@gmail.com> wrote:

I don't see any reason to use the path instead of
decodedPath (other than a bug).  Any thoughts?

The behavior is correct.  One of the three legitimate
reasons characters are escaped in URLs is to *prevent*
them from having their normal meaning in the URL.  You
can't ask the URI class to distinguish the case where
the character is encoded to hide its intention to have
the normal meaning.

If you believe the URI class should threat the
following as being the same URL:

http://foo.com/A/B
http://foo.com/A%2FB

then what do you think it should do with these two?

http://foo.com/A?hello/there
http://foo.com/A%3Fhello/there

Should they have the same meaning?


                
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 

<Prev in Thread] Current Thread [Next in Thread>