HTTP/HTTPS urls doesn't work

[deamme]

States in the documentation that torrentId can be one of the following:

• magnet uri (utf8 string) -
• torrent file (buffer)
• info hash (hex string or buffer)
• parsed torrent (from parse-torrent)
• http/https url to a torrent file (string) - Doesn't work
• filesystem path to a torrent file (string)

[feross]

Are you trying this in the browser? Right now http/https urls to .torrent files don't work there because I completely excluded the simple-get module from the browser. This module makes make the http request, and includes http, which is pretty huge in terms of file size.

Most domains will probably not have the CORS headers configured correctly to allow your website to download the .torrent file. Do you think it's worth adding 50K gzipped, almost doubling the size of the webtorrent library for this feature?

$ browserify -r http | gzip | wc -c
   49400

[deamme]

@feross I see the problem and of course we shouldn't double the size of the library. I'll close this.

[feross]

Actually, maybe this wasn't entirely fair. http includes stream and buffer which are also huge, but those are already included in webtorrent.

$ browserify -r buffer | gzip | wc -c
   10836
$ browserify -r stream | gzip | wc -c
   31852

[deamme]

It could work out then but I don't really see any sites supporting CORS.

[feross]

Actually, I just checked and since we started supporting web seeding, the http module is already being pulled in, so this actually adds just 500 bytes to the file size.

We'll support it.

[feross]

Released as 0.54.0.