WEBAPI issues with uTorrent 2.0.0

I wrote some utilities which make use of the WEBAPI ( Token authentication is being used) and within version 1.8.5, they performs like a charm but in version 2.0.0, I do get a token but calls to for instance the getprops or list functions occurs me the error 300 back. It is looking so wired .This means I have to revert back to version 1.8.5..

Has something configured or is it a error . The weirdest thing is that the webui performs just well. The issues that I encounter happen with uTorrent 2.0.0 in combination with webui 0.362 and 0.370

Are you grabbing the token properly.If you are having any confusion regarding this. so you can come across that and resolve what are the confusions that you have currently . I am here with some new ideas, but here's what I have:

index.html involves somewhere in it, $$TOKEN$$, for example:
<div id='token' style='display:none;'>$$TOKEN$$</div>

It's necessary that it should be placed somewhere accessible from Javascript, but disappeared from the user. uTorrent will replace $$TOKEN$$ when it transfer the file with an opaque token value: .

<div id='token' style='display:none;'>
Repplaced contents ......
</div>

1- Primarily what I have to do is :
http://<username>:<password>@<host>:<port>/gui/token.html

2- After that is to grab the contents of the tag with the id "token" and save that as the token. So that would be any type of contents within the "<div id='token' style='display:none;'>" and "</div>"

3- Then I grab the complete list with:
http://<username>:<password>@{host}:{port}/gui/?list=1&token=<token>

4- Then I found the properties for every specified torrent with:
http://<username>:<password>@<host>:<port>/gui/?action=getprops&hash=<torrent hash>&token=<token>

5- After all, I would configure certain features with:
http://<username>:<password>@<host>:<port>/gui/?action=setprops&hash=<hash>&s=<setting>&v=<value>&token=<token>

In addition, I should also configure the label or start/stop/forcestart a torrent . As I told above , this performed very well in 1.8.5 but in 2.0.0 any action (like list= or action=) will result in an error 300... Anything within the < and > would be replaced by it's main content...

You are going in fine way and Big Fish suggested very well to resolve your confusion but there is something that you need to consider about and try to implement this and would work like charm also ..Add the following components:

Quote:

---

http://<username>:<password>@<host>:<port>/gui/?token=<token>&action=getprops&hash=<torrent hash>

---