Percent encoding: a plus sign is not always a space

A URL component can represent bytes using a percent sign followed by two hexadecimal digits. A space is commonly represented as %20. The literal plus sign has different treatment in different URL-related formats.

Work through it

Compare a raw component with application/x-www-form-urlencoded data. In the latter, + represents a space and a literal plus is normally %2B. A general percent decoder should not automatically impose form-data rules on every path or component.

Keep the interpretation precise

Decode only the component and format you actually have. A full URL contains structural delimiters whose meaning can change if the entire string is decoded at once. Repeated decoding can also change data unexpectedly: %2520 becomes %20 after one pass and a space after a second.

Try it on paper

For a form-data value, predict A+B as A B and A%2BB as A+B. For a general component, record whether + is preserved. State the intended decoder before comparing results, and avoid using secret or authenticated URLs as classroom examples.

Compare and record

Explore our classical cipher tools and cryptography guides alongside the exercise. Record the exact input, operation, key or alphabet convention, expected result and observed result. Change one assumption at a time if they disagree.

Disclosure: original educational material published on behalf of Caesar Cipher, with AI assistance. Contact: contact@caesarcipher.org. Historical ciphers and encodings are learning topics, not a substitute for modern security.