News for hackers. Stuff that matters.

A comment on S3: Plus sign is interpreted as space in the path part of URLs. Parent comment

Re:S3: Plus sign is interpreted as space in the path part of... by jamix on Wednesday October 04, 2017 @07:27AM (#15399702)
Exactly! The OP's point is summarized in this sentence:

> My point is that the spec requires + to be escaped only inside the querystring.

So what? What the standard mandates for query strings is irrelevant here. It's up to the server how to interpret and map the URLs. "Unconventional and unfortunate" - yes, but breaking the HTTP spec? No.

[ Parent | on HN ]
Re:S3: Plus sign is interpreted as space in the path part of... by zAy0LfpBZLC8mAC on Wednesday October 04, 2017 @08:23AM (#15399930)
Please read the actual spec before telling poeple whether something is conforming to it or not. Just making stuff up is exactly how this mess is created. The relevant section in this case:

https://tools.ietf.org/html/rfc3986#section-6.2.2.2

[ Parent | on HN ]
Re:S3: Plus sign is interpreted as space in the path part of... by jchw on Wednesday October 04, 2017 @07:37AM (#15399743)
It breaks the HTTP spec because it internally is decoding the URL wrong. This is important because things that speak HTTP are free to choose to percent encode, or not, the plus sign in a path, and the canonical URL should not differ. If it mapped even an escaped plus to a space, it'd be consistent, though still questionable, behavior.
[ Parent | on HN ]