URL encoding: Difference between revisions

URL encoding (view source)

76 bytes added , 12 years ago

Add another variation: lowercase escapes like %3a. Encoders that always use uppercase escapes are still valid.

Anonymous user

Revision as of 16:52, 13 August 2011 (view source) rosettacode>Markhobley m (therefore content now in leading explanation) ← Older edit		Revision as of 04:42, 14 August 2011 (view source) rosettacode>Kernigh (Add another variation: lowercase escapes like %3a. Encoders that always use uppercase escapes are still valid.) Newer edit →
Line 19: '''Variations''' * Lowercase escapes are legal, as in "<code><nowiki>http%3a%2f%2ffoo%20bar%2f</nowiki></code>". ~~Note~~* ~~that some~~Some standards give different rules: RFC 3986, ''Uniform Resource Identifier (URI): Generic Syntax'', section 2.3, says that "-._~" should not be encoded. HTML 5, section [http://www.whatwg.org/specs/web-apps/current-work/multipage/association-of-controls-and-forms.html#url-encoded-form-data 4.10.22.5 URL-encoded form data], says to preserve "-._*", and to encode space " " to "+". The options below provide for utilization of an exception string, enabling preservation (non encoding) of particular characters to meet specific standards. '''Options''' It is permissible ~~for~~to use an exception string (containing a set of symbols that do not need to be converted) ~~to be utilized~~. However, this is an optional feature and is not a requirement of this task. '''See also'''