"I personally wouldn't call it an "issue" because AFAIK it's optional whether spaces should be escaped as %20 or +, ..."
If you look in the paragraph where I used the word "issue", you'll see:
"It would make sense that the escaping mechanism was consistent across modules in the same distribution"
I consider the inconsistency to be an issue. I made no reference to %20 or + being better, preferred, more correct, or anything else of that ilk.
"... and it's been that way for a long time."
Yes, I know. I was coding such escapes more than two decades ago.
"From URI's Changes file:"
I would question the relevance of including that entry from almost 22 years ago; it even references HTML4 which certainly isn't current. All that I'm getting from it is: "We changed %20 to + in some places, even though we believed that to be wrong, and left everything else in an inconsistent state".
— Ken
In reply to Re^3: How encode space into %20 in URI
by kcott
in thread How encode space into %20 in URI
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |