By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,131 Members | 1,494 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,131 IT Pros & Developers. It's quick & easy.

asp server.UrlEncode VS asp.net Server.UrlEncode Vs Php urlencode

P: n/a
Hi,

what's the difference about Asp Server.UrlEncode and the Asp.Net
Server.UrlEncode ?

In asp:
Server.UrlEncode("*") = %2A

In Asp.Net:
Server.UrlEncode("*") = *

In Php
urlencode("*") = %2A

why ?


Nov 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Dario
You want to read RFC2396 (http://www.ietf.org/rfc/rfc2396.txt) to understand
what is valid in a URI.

Section 2.3 deals with unreserved characters (which * is a part of) and
says:

" Unreserved characters can be escaped without changing the semantics of the
URI, but this should not be done unless the URI is being used in a context
that does not allow the unescaped character to appear."

which, to me, implies ASP.Net is likely doing it right..

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Dario Sala" <da********@studiofarma.it> wrote in message
news:cn**********@news.ngi.it...
Hi,

what's the difference about Asp Server.UrlEncode and the Asp.Net
Server.UrlEncode ?

In asp:
Server.UrlEncode("*") = %2A

In Asp.Net:
Server.UrlEncode("*") = *

In Php
urlencode("*") = %2A

why ?

Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.