Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

HTTP 301 Moved Permanently redirection fails

by Zeus on 2015/01/17 02:02:11 AM    
The HTTP header for "Host" does not contain the port number Tixati used to access the tracker. If the redirection "Location" URL uses the port number in the HTTP header (none in this case) then the redirection will not go to the correct port, rather to the default port 80 and will fail with a timeout.
by Napsterbater on 2015/01/17 10:25:54 PM    
I have the same problem on probably the same site (that cant be named).

HTTP 301 Moved Permanently redirection is working correctly, but Tixati is sending the wrong info in the initial HTTP Get request.


Say we have tracker tracker.blah.com:8080, Tixati should set the HTTP HOST field to tracker.blah.com:8080, but it dosn't it sends tracker.blah.com.

Now the way the redirection works for this site is it see HOST tracker.blah.com and says redirect to tracker01.blah.com as you can see no port given, so then Tixati trys tracker01.blah.com with no response.

But if you send the same GET request to tracker.blah.com:8080 with the HOST field set to tracker.blah.com:8080 then it sends back redirect to tracker01.blah.com:8080


Info here.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23




This web site is powered by Super Simple Server