I am using Transmission 2.92 (14714) (but I am pretty sure I have seen this on maaany versions before).
Sometimes I enter too short URL in my browser and land on the unfriendly HTTP 409 page instead of Transmission web UI.
I have reproduced it with curl:
root@host:~# curl -H "Authorization: Basic (...)" -v http://192.168.100.100:9091/transmission/
> GET /transmission/ HTTP/1.1
> Host: 192.168.100.100:9091
> User-Agent: curl/7.51.0
> Accept: */*
> Authorization: Basic (...)
>
< HTTP/1.1 409 Conflict
< Server: Transmission
< X-Transmission-Session-Id: (...)
< Date: Mon, 27 Mar 2017 22:16:52 GMT
< Content-Length: 580
< Content-Type: text/html; charset=ISO-8859-1
<
<h1>409: Conflict</h1><p>Your request had an invalid session-id header.</p><p>To fix this, follow these steps:<ol><li> When reading a response, get its X-Transmission-Session-Id header and remember it<li> Add the updated header to your outgoing requests<li> When you get this 409 error message, resend your request with the updated header</ol></p><p>This requirement has been added to help prevent <a href="http://en.wikipedia.org/wiki/Cross-site_request_forgery">CSRF</a> attacks.</p><p><code>X-Transmission-Session-Id: (...)</code></p>
It's not really a big deal but it would be nice if this could be polished.
I am using Transmission 2.92 (14714) (but I am pretty sure I have seen this on maaany versions before).
Sometimes I enter too short URL in my browser and land on the unfriendly HTTP 409 page instead of Transmission web UI.
I have reproduced it with curl:
It's not really a big deal but it would be nice if this could be polished.