This works, the web seed link is visible to Transmission and it can download the file from the web server. Seeding is still needed from another location, since the client needs meta information from the seeder.
However, after adding multiple links as web seed the download does not start at all. Only one web seed is visible to Transmission:
I would like to test the web seed feature on a web hoster, where the directory is physically on the server and accessable, but I am too lazy for this now:
I have created the test file "nom.img" and uploaded it to "gofile.io":
https://gofile.io/d/uK3NAc
I then created a Torrent file like so:
$ mktorrent --web-seed="https://srv-store3.gofile.io/download/uK3NAc/3566de3a97906ed..." --output="nom.img.torrent" nom.img
This works, the web seed link is visible to Transmission and it can download the file from the web server. Seeding is still needed from another location, since the client needs meta information from the seeder.
However, after adding multiple links as web seed the download does not start at all. Only one web seed is visible to Transmission:
$ mktorrent --web-seed="https://srv-store3.gofile.io/download/uK3NAc/3566de3a97906ed..." --output="nom.img_nom.img.b2.torrent" nom2
$ mktorrent --web-seed="https://srv-store3.gofile.io/download/uK3NAc/3566de3a97906ed..." --web-seed="https://srv-store2.gofile.io/download/uK3NAc/712fbfb75b98f27..." --output="nom.img_nom.img.b2_2.torrent" nom2
I would like to test the web seed feature on a web hoster, where the directory is physically on the server and accessable, but I am too lazy for this now:
$ mktorrent --web-seed="https://<domain_name>.<tld>/nom2/" --output="nom.img_nom.img.b2.torrent" nom2
Something is going on with this weird protocol or I do not see important things.
-Keks