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

WebSeed download gets stuck #432

Closed
bertofer opened this issue Sep 12, 2015 · 2 comments
Closed

WebSeed download gets stuck #432

bertofer opened this issue Sep 12, 2015 · 2 comments

Comments

@bertofer
Copy link

@bertofer bertofer commented Sep 12, 2015

Hi, i'm trying to webseed from a file in localhost. After changing some code, because of the Buffer (feross/simple-get#7 and https://github.com/feross/bittorrent-swarm/issues/22) i cannot get the full file, and got stuck in a small percentage.

Here's all the pastebin of the logs.

http://pastebin.com/c9XRwxtM

I'm investigating why of this behaviour, will post it if a find something. In the meanwhile, I post it here so if anyone could help.

Thanks!

@bertofer

This comment has been minimized.

Copy link
Author

@bertofer bertofer commented Sep 14, 2015

I'm getting error when receiving some pieces, that the peer is choking, but in fact i have received well the request of the pieces with data (At least the first 7). It seems like if the requests are not completed somewhere and it doesn't move forward to other pieces until got timeout and choke.

Porobably has something to do with the browser limit of sockets connection?

@bertofer

This comment has been minimized.

Copy link
Author

@bertofer bertofer commented Sep 16, 2015

Ok, all the problem was that i was sending the data with utf-8, and it isn't guaranteed that buffer -> utf-8 -> buffer, the second buffer to be the same as the first!

Solved it using 'hex' encoding with an express server. I'm now trying nginx to serve statics to see if i need to change the encoding or create the new buffer. I close this issue

@bertofer bertofer closed this Sep 16, 2015
@lock lock bot locked as resolved and limited conversation to collaborators May 6, 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
1 participant
You can’t perform that action at this time.