On 05/13/2014 at 10:29 AM, "Daniel Stenberg" <daniel_at_haxx.se> wrote:
> Sorry, but that's false. Allow me to quote RFC 3986 section 3.1
> about the "scheme" part (which is what we're talking about here):
>
> An implementation should accept uppercase letters as equivalent to
> lowercase in scheme names (e.g., allow "HTTP" as well as "http")
>
> I don't think that leaves much interpretation. Do you?

I don't. Nevertheless, when manipulating strings, we all now that equivalent doesn't mean equal.

sha1('a') != sha1('A')

In my view, the problem isn't the compliance with the RFC (it is compliant) but as you rightly put it:

> I'm mostly saying this isn't a bug. I still agree that it would be
> nicer to use the same lowercase name for all scenarios you
> show. A matter of niceness, not correctness.

It's not a bug but a behavior that could be improved.

> You feel like producing a patch?

Sure, I can give it a try, just give me some leads about where to look.

Best,
Marc

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-05-13