Changeset 11736


Ignore:
Timestamp:
Jan 21, 2011, 2:40:33 AM (11 years ago)
Author:
jordan
Message:

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

Add documentation for handling 409 error messages from the Transmission RPC server.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/extras/rpc-spec.txt

    r11735 r11736  
    4545   since the port and path may be changed to allow mapping and/or multiple
    4646   daemons to run on a single server.
     47
     482.4.  CSRF Protection
     49
     50   Most Transmission RPC servers require a X-Transmission-Session-Id
     51   header to be sent with requests, to prevent CSRF attacks.
     52
     53   When your request has the wrong id -- such as when you send your first
     54   request, or when the server expires the CSRF token -- the
     55   Transmission RPC server will return an HTTP 409 error with the
     56   right X-Transmission-Session-Id in its own headers.
     57
     58   So, the correct way to handle a 409 response is to update your
     59   X-Transmission-Session-Id and to resend the previous request.
    4760
    48613.  Torrent Requests
Note: See TracChangeset for help on using the changeset viewer.