Skip to content

/ webtorrent

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

server: ignore invalid range handers instead of throwing #921

Merged
merged 1 commit into from Sep 18, 2016
Merged

server: ignore invalid range handers instead of throwing #921

merged 1 commit into from Sep 18, 2016

Conversation

@feross
Copy link
Member

feross commented Sep 18, 2016

Fixes: #920
@feross feross mentioned this pull request Sep 18, 2016
Closed
@feross
server: Handle invalid range handers instead of throwing
Loading status checks…
1a0f0ec 
Fixes: #920
@feross feross force-pushed the fix-920 branch from 4de00ac to 1a0f0ec Sep 18, 2016
@dcposch dcposch changed the title server: Handle invalid range handers instead of throwing server: ignore invalid range handers instead of throwing Sep 18, 2016
@dcposch
dcposch reviewed Sep 18, 2016
View changes
Copy link
Contributor

dcposch left a comment

LGTM
@dcposch
dcposch approved these changes Sep 18, 2016
View changes
Copy link
Contributor

dcposch left a comment

LGTM
@dcposch dcposch merged commit 2c8678c into master Sep 18, 2016
5 checks passed
5 checks passed
Node Security No known vulnerabilities found
Details
continuous-integration/appveyor/branch AppVeyor build succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@feross feross deleted the fix-920 branch Sep 18, 2016
@feross

This comment has been minimized.

Sign in to view
Copy link
Member Author

feross commented Sep 18, 2016 •
edited

0.97.1
@lock

This comment has been minimized.

Sign in to view
Copy link

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.
Reviewers

@dcposch dcposch

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
@feross @dcposch
You can’t perform that action at this time.