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

I got stuck. #43

Closed
lagun opened this issue May 7, 2016 · 7 comments
Closed

I got stuck. #43

lagun opened this issue May 7, 2016 · 7 comments

Comments

@lagun
Copy link

lagun commented May 7, 2016

firefox 46.0.1 32bit
tdm version 0.2.7
i can't download complete.

this url
https://singularlabs.com/download/10294/
from this site
https://singularlabs.com/software/system-ninja/confirm-download/
picture
http://postimg.org/image/fvnnyy9mp/

@inbasic
Copy link
Owner

inbasic commented May 7, 2016

This server claims that it supports segmentation, though the server is not responding to the ranged headers. This is a server side issue and cannot be fixed.

You can get files from this server by reducing the number of threads to one.

@inbasic inbasic closed this as completed May 7, 2016
@MariasStory
Copy link

Shouldn't turbo-download-manager check it automatically and have a fallback for this situation?

@inbasic
Copy link
Owner

inbasic commented May 8, 2016

@MariasStory TDM does check for multi-threading support. The problem is with this particular server as it is claiming they support multi-threading. Beside sending the supporting header, they return 206 status code which is sent when a partial data is transmitted. So there is no way for TDM to detect the server is not handling the request as it is supposed to.

So is this happening for another domain too?

@lagun
Copy link
Author

lagun commented May 8, 2016

Thank you for explain.

@MariasStory
Copy link

@inbasic I did not see this happening for another domains. But, where one case, another may follow.

Maybe, there is a way to check for such misleading server behavior?

@inbasic
Copy link
Owner

inbasic commented May 8, 2016

That seems very rare situation for a server to send two wrong signals;

  1. wrong header
  2. 206 status code instead of 200.

Either of these two signals will lead TDM to throw an error message to warn user or reduce the number of threads to one and continue the job if possible.

I am not aware of any other checking methods.

@MariasStory
Copy link

OK. If there is the warning and proposed solution in it, this should not be a problem.

The download attempt with one thread could be started automatically, plus the warn. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants