unforgiving Posted March 2, 2012 Report Share Posted March 2, 2012 Hi, I'm recoding a mirc addon to get WEBUI info, in the old code I used to retrieve the token from this url was: /gui/token.html , but in the new versions of utorrent 3 and above doesn't work anymore. I figure out that the url used now is: /gui/token.html?t=SOMENUMBER . I just need to know, what is this number that come after "t=" ?thanks in advance. Link to comment Share on other sites More sharing options...
Sanity Posted March 6, 2012 Report Share Posted March 6, 2012 Nothing has changed in regards to how you obtain the token. Make sure you are using the name and password (converted to base64) you have setup for the webui to obtain the token. Link to comment Share on other sites More sharing options...
Ultima Posted March 24, 2012 Report Share Posted March 24, 2012 Are you unable to get the token, or are you unable to use the token? Link to comment Share on other sites More sharing options...
klor Posted March 24, 2012 Report Share Posted March 24, 2012 To specifically answer the question, the number after "t=" in the WebUI is the javascript date.now() i.e. milliseconds since the Unix epoch. Link to comment Share on other sites More sharing options...
Ultima Posted March 24, 2012 Report Share Posted March 24, 2012 Context: To the backend, the GET parameter is entirely garbage. For all the backend cares, it could have been t=Math.random() and it would've worked just the same. The only point behind that parameter's use in WebUI was to prevent browsers from pointlessly caching token.html.Basically, you're running down the wrong rabbit hole. Link to comment Share on other sites More sharing options...
unforgiving Posted March 24, 2012 Author Report Share Posted March 24, 2012 thanks for answers, my problems has been solved, my irc addon to Webui is working now. was my fault, my code was wrong. Link to comment Share on other sites More sharing options...
klor Posted March 25, 2012 Report Share Posted March 25, 2012 @Ultima: thanks for the context, I was almost going to say it seemed to be just a random number, but had nothing to base that on. It's probably easier to just always pass the t= parameter to make sure the APIs we use don't go caching on us unexpectedly. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.