search

kylewooten / transdroid

Automatically exported from code.google.com/p/transdroid
GNU General Public License v3.0
0 stars 0 forks source link

409 HTTP Status code on every refresh from transdroid #494

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
utilize apache ProxyPass to proxy request through ssl tunnel

What version of the product are you using?
1.1.15

What torrent client are you using?
transmission-daemon 2.82 (14160)

Watching logfiles while transdroid is refreshing its Torrent list I found a 
strange Pattern of 401 (Unathorized)HTTP codes in my logfiles:

transdroid-ip-address - - [29/Sep/2013:13:00:03 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 5667 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:03 +0200] "POST /transmission/rpc 
HTTP/1.1" 409 935 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:03 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 504 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:03 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 1889 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:03 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 370 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:03 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 7677 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:14 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 504 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:14 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 1889 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:15 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 370 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:16 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 7677 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:16 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 370 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:16 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 1889 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:17 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 5667 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:17 +0200] "POST /transmission/rpc 
HTTP/1.1" 409 935 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:18 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 504 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:18 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 1889 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:18 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 370 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:18 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 9548 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:18 +0200] "POST /transmission/rpc 
HTTP/1.1" 401 370 "-" "-"
transdroid-ip-address - - [29/Sep/2013:13:00:18 +0200] "POST /transmission/rpc 
HTTP/1.1" 200 1335 "-" "-"

Transdroid is fully working listing and refreshing torrents is working (the 200 
OK HTTP Code also indicates that)
Strangely those 409 are poping up every refresh transdroid does.

If any additional information is needed feel free to contact me.

Original issue reported on code.google.com by Hendrik....@googlemail.com on 29 Sep 2013 at 12:22

GoogleCodeExporter commented 9 years ago 
additional information: this dose NOT happen if I use transmission-remote 
(http://code.google.com/p/transmisson-remote-gui/) over the same configuration.

Original comment by Hendrik....@googlemail.com on 29 Sep 2013 at 12:28

GoogleCodeExporter commented 9 years ago 
additional information: this bug is also in transdroid2-beta4.

Original comment by Hendrik....@googlemail.com on 29 Sep 2013 at 12:49

GoogleCodeExporter commented 9 years ago 
HTTP 409 errors are returned by Transmission to provide a unique session token. 
Transdroid uses these in subsequent requests to get access to the API 
correctly. This token should be cached during every Transdroid 'session' but 
these session might last only one screen. I'll check it out and see if I can 
improve on that.

Original comment by erickok@gmail.com on 30 Sep 2013 at 2:29

GoogleCodeExporter commented 9 years ago 
Oh shit, it seems i am a total idiot.
I did _not_ mean the occasional 409 requests. Instead I meant the 401 error 
codes.
Those do occur in companion of the successful 200 Code.
Sorry for writing 409. I did mean 401 ;(

Original comment by Hendrik....@googlemail.com on 30 Sep 2013 at 2:49