Transmission/transmission
1
0
Fork 0
mirror of https://github.com/transmission/transmission.git synced 2025-12-20 02:18:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

#3915 "RPC Documentation should reflect in the X-Transmission-Session-Id headers" -- fixed.

Browse Source 
Add documentation for handling 409 error messages from the Transmission RPC server.
This commit is contained in:
Jordan Lee
2011-01-21 02:40:33 +00:00
parent ab02ba0d2c
commit 09d28baeb4
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
extras/rpc-spec.txt
View File

@@ -45,6 +45,19 @@
since the port and path may be changed to allow mapping and/or multiple since the port and path may be changed to allow mapping and/or multiple
daemons to run on a single server. daemons to run on a single server.
2.4. CSRF Protection
Most Transmission RPC servers require a X-Transmission-Session-Id
header to be sent with requests, to prevent CSRF attacks.
When your request has the wrong id -- such as when you send your first
request, or when the server expires the CSRF token -- the
Transmission RPC server will return an HTTP 409 error with the
right X-Transmission-Session-Id in its own headers.
So, the correct way to handle a 409 response is to update your
X-Transmission-Session-Id and to resend the previous request.
3. Torrent Requests 3. Torrent Requests
3.1. Torrent Action Requests 3.1. Torrent Action Requests