If Url can contans '=='

just a quick one that if an url can contains character like '==' ?

eg.
uMm8PMN9seYA9vJd2IqZCg==
LVL 1
doramail05Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tpaynCommented:
No you will need to encode special characters. http://www.w3schools.com/tags/ref_urlencode.asp

You could use the following to encode and decode:


string encoded = HttpServerUtility.UrlTokenEncode(Encoding.UTF8.GetBytes(stringtoencode));

string decoded = Encoding.UTF8.GetString(HttpServerUtility.UrlTokenDecode(encoded));

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alfred A.Commented:
Check this link out:

http://www.ietf.org/rfc/rfc1738.txt

Check section 2.2. URL Character Encoding Issues for details especially on the reserved character part as equal (=) sign is a reserved character.  However, it looks like '==' is allowed.

I guess to be sure, if it is possible, encode the characters you need to include in URL.
Alfred A.Commented:
By the way, I provided a specification that has been superseded by rfc2396.

Check the link below:

http://www.ietf.org/rfc/rfc2396.txt

Equal sign (=) is still considered a reserved character.  Quoting section 2.2 of the specification:

   Many URI include components consisting of or delimited by, certain
   special characters.  These characters are called "reserved", since
   their usage within the URI component is limited to their reserved
   purpose.  If the data for a URI component would conflict with the
   reserved purpose, then the conflicting data must be escaped before
   forming the URI.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
C#

From novice to tech pro — start learning today.