Talk:URL encoding: Difference between revisions

: --[[User:Dgamey|Dgamey]] 09:54, 17 June 2011 (UTC)

The point of encoding strings is to avoid confusion. Some characters, such as '+' and '?', tend to be metacharaters used by CGI interface (? for begining of query string, + for separating parameters), while '\r' '\n' must be encoded because they signify end of input; also encoding can carry whatever text not in low 127 bits and printable with "normal text", so dumber server or client software won't get totally confused. I don't know how much we need to conform to various RFCs here, maybe common sense would suffice. In principle you can escape the "http" too, and still conform to most standards, but that would be utterly pointless, wouldn't it? --[[User:Ledrug|Ledrug]] 02:23, 19 June 2011 (UTC)