uTorrent doesn't seem to respect 301 Moved Permanently

[medecau]

I am developing an app that redirects clients to a tracker, redirection is done with HTTP code 301 Moved Permanently.

From the logs i see clients that keep coming to the same tracker url after being served a code 301.

I have presented this in IRC freenode.net/#bittorrent and it seems i am not the only one experiencing this.

HTTP code 301:

The requested resource has been assigned a new permanent URI and any

future references to this resource SHOULD use one of the returned

URIs.

HTTP code 302:

The requested resource resides temporarily under a different URI.

Since the redirection might be altered on occasion, the client SHOULD

continue to use the Request-URI for future requests.

http://tools.ietf.org/html/rfc2616#section-10.3.2

http://tools.ietf.org/html/rfc2616#section-10.3.3

Since BT clients use HTTP to contact trackers i believe it would be an expected behavior to respect the implementation, this forces a huge unnecessary amount of resource consumption on servers redirecting the clients.

[arvid]

Thanks for pointing this out. I agree that we should do this. It's not trivial, since the new URL needs to be saved in the resume data. It will most likely not make it into 2.0, since it's in feature freeze, but it should definitely make it into the release following it.

[medecau]

i have been talking with some guys in the IRC channel, i believe some are Azureus devs, and ti might be a good policy to either only remember the new address for the duration of the session like the peer_id or store along with the original tracker.

But this is up to you guys.

Thanks for your time.