URL Encoding Guide: Percent-Encoding for Developers
Complete guide to URL encoding: which characters must be encoded, the %XX format, reserved vs unreserved characters, and common mistakes to avoid.
Published:
Tags: encoding, url, developer-tools
URL Encoding Guide: Percent-Encoding for Developers URLs can only contain a limited set of characters. The moment you put a space, an ampersand, or a non-ASCII character into a URL, things break — silently and in ways that are hard to debug. URL encoding (formally called percent-encoding) is the mechanism that solves this, and understanding it at the RFC level will save you hours of head-scratching. This guide covers what URL encoding is, which characters must be encoded and why, and the mistakes developers make most often. The RFC 3986 Character Classes RFC 3986 divides characters into two groups. Unreserved Characters These 66 characters are safe to appear anywhere in a URL without encoding: That's it. Just letters, digits, hyphen, underscore, period, and tilde. If a character is not in…
All articles · theproductguy.in