Page 1 of 1
409 Conflict
Posted: Mon Sep 26, 2011 1:40 am
by oneadvent
Hi!
I am getting this when I go to: localhost:9091/transmission/rpc
but I need that to work for a program I am using it with (mediafrontpage). Can I get some direction to how to solve this?
Thanks!
409: Conflict
Your request had an invalid session-id header.
To fix this, follow these steps:
When reading a response, get its X-Transmission-Session-Id header and remember it
Add the updated header to your outgoing requests
When you get this 409 error message, resend your request with the updated header
This requirement has been added to help prevent CSRF attacks.
X-Transmission-Session-Id: Qt0jLxQvilI1f2oJzdpB8iS73v9uhUxtfpwYHbVgVlPSv6lZ
Re: 409 Conflict
Posted: Mon Sep 26, 2011 7:53 pm
by gunzip
i don't know but there might be something in this forum thread that might help:
Error 409: Web UI and Apache
Re: 409 Conflict
Posted: Mon Sep 26, 2011 8:52 pm
by Jordan
By default, Transmission requires the session-id token to prevent csrf exploits.
If you want to disable the 409 test in order to get it to work with some other software, remove the line that says "#define REQUIRE_SESSION_ID" in libtransmission/rpc-server.c and rebuild Transmission.
Re: 409 Conflict
Posted: Mon Sep 26, 2011 10:44 pm
by oneadvent
Okay I have literally been trying all day to compile it and I just get error after error. Can't we just get an option for that? Is there another version I can download?
Re: 409 Conflict
Posted: Mon Sep 26, 2011 10:53 pm
by Jordan
No, there's not a configurable option for that.
What compile error are you getting?
Re: 409 Conflict
Posted: Mon Sep 26, 2011 11:10 pm
by oneadvent
Code: Select all
make[1]: Leaving directory `/home/oneadvent/source/Transmission/third-party'
Making install in libtransmission
make[1]: Entering directory `/home/oneadvent/source/Transmission/libtransmission'
CC announcer.o
announcer.c:19:27: fatal error: event2/buffer.h: No such file or directory
compilation terminated.
make[1]: *** [announcer.o] Error 1
make[1]: Leaving directory `/home/oneadvent/source/Transmission/libtransmission'
make: *** [install-recursive] Error 1
Re: 409 Conflict
Posted: Mon Sep 26, 2011 11:46 pm
by Jordan
viewtopic.php?f=2&t=11234
You need the dev headers for libevent2.
Re: 409 Conflict
Posted: Tue Sep 27, 2011 12:29 am
by oneadvent
Code: Select all
oneadvent@oneadvent-desktop:~$ sudo apt-get install libevent2-dev
[sudo] password for oneadvent:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libevent2-dev
oneadvent@oneadvent-desktop:~$ sudo apt-get install libevent-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libevent-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
oneadvent@oneadvent-desktop:~$
I am using Ubuntu
Re: 409 Conflict
Posted: Tue Feb 07, 2012 11:53 pm
by greniesa
I have a question, why exactly it does that.
I just want to acces my Transmission, so why it doesnt work.
What do I have to do for it to work without compiling? Do I have to wait or what?
I read ther solution and I dont understand a thing:
"Your request had an invalid session-id header.
To fix this, follow these steps:
When reading a response, get its X-Transmission-Session-Id header and remember it
Add the updated header to your outgoing requests <-- HOW do I achieve that?
When you get this 409 error message, resend your request with the updated header
This requirement has been added to help prevent CSRF attacks.
X-Transmission-Session-Id: ...yhfa..."
I understand it's for my security... I dont necesseraly want to break this feature, I just want to understand how it work.
Re: 409 Conflict
Posted: Wed Feb 08, 2012 8:31 am
by killemov
If you just want to use the stock web-ui with the stock transmission-daemon you should not have to compile anything yourself. My guess is you just ran into a small problem with the exact url. http://host:port/transmission/web/
Re: 409 Conflict
Posted: Sat Mar 10, 2018 5:31 pm
by slight001
Battled with this for a little while, but the solve is so easy I'm embarrassed...
Make sure you place the following slash (e.g. 192.168.0.2:9091/transmission/web/)
hope this helps
