a few pedantic (lazy) questions,

no desire to rathole - just curious -

the bnf in https://tools.ietf.org/html/rfc1738 describes scheme as

       <scheme>:<scheme-specific-part>

is libcurl consistent in normalising :// after any defined/supported
schemes ? specifically wondering if the heuristics first check with
file:// if no scheme is supplied ?

otherwise +1 to Erik's response eg. sounds like something to be kept
as is with the ability to configure fallback.

Jim

On Wed, 19 Sep 2018 at 11:11, Daniel Stenberg via curl-library
<curl-library_at_cool.haxx.se> wrote:
>
> Hi!
>
> 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.
>
> (Brought to attention since I'm adding the CURLU_GUESS_SCHEME to the URL API
> in https://github.com/curl/curl/pull/3018)
>
> Thoughts?
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-09-19