- Name: SWeidner
- Location: Elk Point, South Dakota, United States
My Blogger Code
B5 d+ t k s u- f- i- o- x-- e l- c (decode it!)
My Geek Code
GAT/IT d-(+) s+(): a C+++$ ULC+++>$ P++>++++ L++$>++++ !E W++>$ N+ !o !K w+()@ !O !M- !V PS-(--)@>--- PE+ Y-- PGP>++ t+ !5(-) X+ !R- tv-(+)? b+ DI++++ D++>$ G e+>++ h----(-) r+++ y++++
Steve's random ramblings and technical notes
Monday, October 25, 2004
URL Encoder and Decoder
Sometimes we get emails, even legitimate ones, that have URLs encoded with "%49" entities. In order to allow certain "bad" characters into a URL in a meaningful way, it is possible to encode them. For example, forward slashes, question marks, spaces, ampersands, etc. all have special meaning in a URL and can break it. But if GET data contains one of these characters, you need to be able to push it through a URL. In comes URL encoding and decoding. But you don't have to stop there. You can encode everything in the URL, and your browser will still manage to figure it out.
When you construct a URL, usually with GET data, you must escape certain characters if present so the URL does not break and the server can parse it correctly. This page encodes URLs in case you need to use one without it being generated by a web server.