RE: [EMAIL PROTECTED] Parsing problem in the encoded Url

Thank you -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Slive Sent: Tuesday, April 03, 2007 6:23 AM To: users@httpd.apache.org Subject: Re: [EMAIL PROTECTED] Parsing problem in the encoded Url On 4/3/07, Alaka Pathy -X (apathy - HCL at Cisco

Re: [EMAIL PROTECTED] Parsing problem in the encoded Url

On 4/3/07, Alaka Pathy -X (apathy - HCL at Cisco) <[EMAIL PROTECTED]> wrote: Thanks Joshua. So you mean to say, when we encode, we should not encode "?" character in the url. Right. (Unless you intend it to be a part of the path, rather than the query-string separator.) Joshua. --

RE: [EMAIL PROTECTED] Parsing problem in the encoded Url

PROTECTED] Parsing problem in the encoded Url On 4/2/07, Alaka Pathy -X (apathy - HCL at Cisco) <[EMAIL PROTECTED]> wrote: > > > Hi All, > > I have an issue with the parsing of the url and getting the original > uri from the url, when the url is encoded. > > When I

Re: [EMAIL PROTECTED] Parsing problem in the encoded Url

On 4/2/07, Alaka Pathy -X (apathy - HCL at Cisco) <[EMAIL PROTECTED]> wrote: Hi All, I have an issue with the parsing of the url and getting the original uri from the url, when the url is encoded. When I access, http://servername:port/hh/test?var1=xyz , then the URI generated here is only /

[EMAIL PROTECTED] Parsing problem in the encoded Url

Hi All, I have an issue with the parsing of the url and getting the original uri from the url, when the url is encoded. When I access, http://servername:port/hh/test?var1=xyz , then the URI generated here is only /hh/test and args is var1=xyz . But