CODEWITHSUNDEEP
httpurlcharacter-encodinguriurlencode
Josh
Josh

Reputation: 12791

Equivalency with percent-encoded URLs

Consider the following two URLs:

  1. https://www.google.com/search?q=foo
  2. https://www.google.com/search%3Fq%3Dfoo

To my knowledge, the second one is the percent-encoded version of the first one, but it returns an error. Why?

Aren't these two URLs technically equivalent as per RFC-3986? Could / should a web server choose to make them equivalent or would that go against the standard?

Upvotes: 0

Views: 51

Answers (1)

Julian Reschke
Julian Reschke

Reputation: 42045

No, they are not. The question mark, when escaped, will lose the special meaning it has otherwise.

Upvotes: 1

Related Questions