Not prepend with authentication information portion of a URL

[Arttse]

Ok, in 1.0.4 you added support to ignore protocols with non colon-slash-slash. But now it not prepend with auth (the authentication information portion of a URL). Example:

const prependHttp = require('prepend-http');

prependHttp('login:[email protected]');
//=> login:[email protected]

prependHttp('login:[email protected]:1234');
//=> login:[email protected]:1234

prependHttp('login:[email protected]/path/name');
//=> login:[email protected]/path/name

In version 1.0.3 it worked correctly.

[sindresorhus]

Basic Auth in the URL is deprecated and strongly recommended against. It was even removed from Chrome. You should rather use a header, or even better, something other than Basic Auth.

http://serverfault.com/a/541206/11987

I would go with a mention in the docs, but if you really need it, I would be open to a good PR with tests.

[Arttse]

It Is not recommended, but still used. This can be useful for someone when working with URLs.

[kevva]

How would you differentiate mailto:[email protected] from login:[email protected]? Otherwise, this would work /^\.*\/|^(?!localhost)(?!\S+(:\S*)?@)\w+:/.test(url).

[Daniel15]

Basic Auth in the URL is deprecated and strongly recommended against.

Digest auth is not deprecated, and can use the same login:[email protected] URL format.

[sindresorhus]

The only way to support this is to let the user decide between only supporting http/https and have auth support or not auth support and have support for the mailto scheme.