Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web seed format jpg and mp4 #885

Closed
yanshekki opened this issue Aug 13, 2016 · 4 comments
Closed

web seed format jpg and mp4 #885

yanshekki opened this issue Aug 13, 2016 · 4 comments
Labels

Comments

@yanshekki
Copy link

@yanshekki yanshekki commented Aug 13, 2016

  • WebTorrent version: v0.96.0
  • Node.js version:
  • Browser name/version (if using WebTorrent in the browser): Chrome

Hi there,

I have some question of addWebSeed function. The problem is addWebSeed not work at jpg files.

sample:
mp4 is work: https://www.extratown.com/webtorrent/download/public/2016/08/13/sintel.mp4
jpg can not work: https://www.extratown.com/webtorrent/download/public/2016/08/13/IMG_20160229_164424-10.jpg

I checked the network mp4 is 206 HTTP_RANGE, but jpg is 200.

Thank you!

@feross feross added the question label Aug 13, 2016
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Aug 13, 2016

I just checked out the links you posted and did some investigation. It appears that your server is returning an invalid response for the jpg file.

WebTorrent makes a request with the following header, to indicate the range it wants:

range:bytes=4456448-4559885

But the server responds with this header, indicating it is returning the wrong bytes:

content-range:bytes 0-4559885/4559886

But for the .mp4 file, it's working fine:

range:bytes=0-262143
content-range:bytes 0-262143/129241752

I have no idea why your server (which looks like cloudflare's nginx) would be doing that. But I don't think this is a WebTorrent bug, so I'm going to close this issue. Feel free to continue discussion and do share what you find out if you solve this!

@feross feross closed this Aug 13, 2016
@yanshekki

This comment has been minimized.

Copy link
Author

@yanshekki yanshekki commented Aug 14, 2016

I am sorry for this is my problem.

The proxy server have cache-control header for some extension, i need to close it.

Thank you for your help.

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Aug 14, 2016

Glad you got it figured out!

@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.