On Wed, Sep 19, 2018 at 2:06 AM Daniel Stenberg via curl-library < [email protected]> 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? > Could this be a perpetually deprecated feature, and brought to light with a setopt NODEPRECATED=1 style tuneable? -bch > -- > > / 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
