Opened 7 years ago
Closed 6 years ago
#5786 closed Bug (invalid)
add-torrent RPC request gets no HTTP response
Reported by: | AmbroseChapel | Owned by: | |
---|---|---|---|
Priority: | Low | Milestone: | None Set |
Component: | Web Client | Version: | 2.82+ |
Severity: | Trivial | Keywords: | rpc, http |
Cc: |
Description
I'm trying to add torrents programmatically to the web interface of Transmission on my NetGear? NAS 102.
I make a request, get a 409 response, read the Session ID header from it, make a second request and ... nothing is returned. There's no HTTP response at all.
It's not 100% clear to me what the address of the RPC endpoint is in this situation.
If I'm accessing the Transmission web interface in a browser and the address is 192.168.0.1:8081/transmission/web, what's the address the RPC request should go to?
The documentation mentions the default URL being http://host:9091/transmission/rpc, so should I be sending the request to
or
or something else?
TIA
Change History (3)
comment:1 Changed 7 years ago by x190
comment:2 Changed 7 years ago by AmbroseChapel
- Type changed from Translation to Bug
comment:3 Changed 6 years ago by mike.dld
- Resolution set to invalid
- Status changed from new to closed
Closing as no additional info was provided in response to comment:1. This looks like support forums material. Reopen if there is a real issue.
Try http://192.168.0.1:8081/transmission/rpc/ with the trailing slash.