Custom Encoding Rules (RFC 1738)
According to RFC 1738, certain characters in URLs must be encoded to ensure safe transmission over the internet. These characters are replaced with a percent sign (%) followed by two hexadecimal digits representing the ASCII value.
-
$(Dollar Sign) →%24
Used in pricing or query strings; must be encoded to avoid ambiguity. -
&(Ampersand) →%26
Separates parameters in query strings; encoding prevents misinterpretation. -
+(Plus) →%2B
Often used to represent spaces in form data; encoding preserves literal plus signs. -
,(Comma) →%2C
Used in lists or coordinates; encoding ensures structural integrity. -
:(Colon) →%3A
Separates scheme from address (e.g.,http:); encoding avoids confusion in data. -
;(Semicolon) →%3B
Sometimes used to delimit parameters; encoding prevents parsing errors. -
=(Equals) →%3D
Assigns values in query strings; encoding preserves literal usage. -
?(Question Mark) →%3F
Begins query string; encoding avoids premature termination. -
@(At Sign) →%40
Used in email addresses and authentication; encoding ensures safe inclusion. -
/(Forward Slash) →%2F
Used to separate path segments in URLs. In path components, it must not be encoded. However, when used in query parameters or data values, it should be encoded to avoid breaking the URL structure.