Lord Alderaan Posted December 1, 2010 Report Share Posted December 1, 2010 I'm getting strange web API behavior.When I connect to the API my first request always results in an error 400 with invalid request in the body. Only the second request using the same connection seems to get properly handled.Likewise when I go to the webui in my browser I always get a Invalid Request and only after pressing F5 do I get to login.Anyone else experiencing this issue? Or is this a bug or even intended behavior?>GET /gui/token.html HTTP/1.1>Authorization: Basic YoMgwtfLOLwutNQ==>Host: 127.0.0.1:12345>Accept: */*>HTTP/1.1 400 ERRORConnection: keep-aliveContent-Length: 17Content-Type: text/htmlinvalid request>GET /gui/token.html HTTP/1.1>Authorization: Basic YoMgwtfLOLwutNQ==>Host: 127.0.0.1:12345>Accept: */*>HTTP/1.1 200 OKConnection: keep-aliveContent-Length: 117Content-Type: text/htmlSet-Cookie: GUID=15C5J05a49bxKSfFBKzc; path=/Cache-Control: no-cache<html><div id='token' style='display:none;'>BawR29ofNfaSNY2UaehUo4AApK8W-SSmXmVUiZLrqmSS5ky1PtEf2HdZ9kw=</div></html> Link to comment Share on other sites More sharing options...
twistedfall Posted December 29, 2010 Report Share Posted December 29, 2010 It happens when you have torrent listening port and webui port set to the same value. uTorrent server specific bug as it seems to me. Link to comment Share on other sites More sharing options...
Lord Alderaan Posted December 29, 2010 Author Report Share Posted December 29, 2010 Thanks! Changing the webui port solved that issue for me. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.