Re: Do "=" chars in request parameters need to be URL-encoded?

The safest bet is any description to be URLEncode, I have this similar
problem and with Encode and Decode it went away and substantiated in
different containers porting.


-----Original Message-----
From: Karr, David [mailto:[email protected]]
Sent: Monday, April 21, 2003 12:34 PM
To: [email protected]
Subject: Do "=" chars in request parameters need to be URL-encoded?


If I have a request parameter value that represents an LDAP
distinguished name, like "low=abc,middle=def,high=ghi", am I required to
URL-encode the "=" characters, so I would have to use
"low%3Dabc,middle%3Ddef,high%3Dghi" instead?

I mostly wonder what the specification states (and where in the
specification it would say this, and which specification).  I noticed
that Tomcat 4.1.18 lets me get away with not encoding them, but a very
old iPlanet installation gets confused if I don't encode them.

___________________________________________________________________________
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html


------------------------------------------------------------------------------

This email is confidential and may be legally privileged.

It is intended solely for the addressee. Access to this email by anyone else,
unless expressly approved by the sender or an authorized addressee, is
unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution
or any action omitted or taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error, please
contact the sender, delete this e-mail and destroy all copies.

==============================================================================