Switch agent to use V2 announce endpoint #292
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
evelynl94
approved these changes
Nov 4, 2020
3a5ea99 to
82f5ab6
Compare
Codecov Report
@@ Coverage Diff @@
## master #292 +/- ##
=======================================
Coverage 64.80% 64.80%
=======================================
Files 186 186
Lines 7822 7822
=======================================
Hits 5069 5069
Misses 1999 1999
Partials 754 754
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is long overdue. We added the V2 endpoint to Tracker over a year ago
and never migrated the agents over.
By using the V2 endpoint, the info hash will be part of the request URL,
and thus our nginx access logs in Tracker will show which info hash is being announced.