On 9/19/2018 5:02 AM, Daniel Stenberg via curl-library wrote:
> The URL parser in libcurl accepts URLs without a scheme, the "text://"
> part of URLs.
>
> If no scheme is specified, libcurl guesses which scheme that was
> intended based on some basic hueristics and if nothing matches it
> falls back to plain old "http://".
>
> In this day and age of growing HTTPS use and slow decay of plain HTTP,
> maybe it is time to change the fallback in libcurl and make it instead
> go with HTTPS if nothing else matches?
>
> I'm a little scared this might hurt a lot of users running scripts
> relying on this since forever.

I'm against it for the reason you mentioned, I consider it a breaking
change.

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-09-19