Add authentication information to the RPC spec #1808
Merged
Conversation
This file contains 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
When writing code that interacted with the Transmission RPC server, I struggled to find any information regarding the authentication method used when auth is enabled. I found the solution with the help of Fishman in IRC, but I think it would be nice if this was documented so other people don't encounter a similar issue.
ckerr
approved these changes
Sep 15, 2021
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.
When writing code that interacted with the Transmission RPC server, I struggled to find any information regarding the authentication method used when auth is enabled on remote connections.
I found the solution with the help of Fishman in IRC, but I think it would be nice if this was documented so other people don't encounter a similar issue.