Does it bugger up on a nearly continuous basis for everybody else? By bugger up I mean appearing to work perfectly up until the download should start upon which appears a Download-session invalid message. Also get the problems of it thinking I've downloaded stuff when I haven't.
Anybody got any ideas of how to solve this? Seeing as most of the good shit is hosted on RapidShare and all.
Name:
Anonymous2006-06-09 16:58
Guys, the Rapidshare issue is pretty simple. For ages, ntl has used webcaching, they've got a few big machines that store commonly viewed page, to reduce loading time, they just chuck you their copy.
If you go to a site not on there, or a forced reload thing, the webcache machine will request it from the server. Now, most code will see past the proxy and get your actual ip, and let you download.
However, the coding used in rapidshare's setup is not compatible with the webcache proxy setup used by ntl (AND SOMEWHAT MORE RECENTLY, BT AS WELL), so it only see's the PROXY's ip address.
Hence, it thinks that you're either ALL of BT, and says you've downloaded too much/currently downloading, or it says you're requesting from the wrong ip (the proxy ip requests, your ip receives, it doesn't like that)
If you manually configure your browser/OS to use the http proxy webcache.bt.net:8080 then you won't get the "download session invalid" message. Unfortunately, it will still get you on the first "You have downloaded 50GB Want tod ownload more? Wait till THE END OF TIME".
So you can either enter a mad dash competition with the rest of BT (I've done this a couple of times for stuff I really needed), or you're screwed.
I'm gonna try and get in touch with someone at BT who knows what they're doing (HAHAHAHAHAHA), and tell them to either bypass the proxy for all rapidshare.de connections, or turn the webcache off completely for my connection. After all, my connection was always fine before they turned it on..