c**tplaces said:
clunk said:
Mind you, I just pinged www.c**tplaces.co.uk and it just timed out. :-\
Thats because I block ICMP which is a protocol used in the ping process.
It's also used in TCP so you'll screw anyone who uses a route that's a bit iffy, they'll have to rely on the client sensing a timeout and asking for a complete file again instead of TCP just asking for the lost packet.
I imagine the server's the problem. It probably sees who's connecting and thinks "Oh it's that Whitelackington again, I'll make him wait".
WL - BTInternet as it was then called used to use a system of caching, rather like the local store of web pages on your PC only somewhere on the connection you pay for. It's supposed to speed things up when you or anyone else keep asking for the same page, they, your ISP, just send you their own copy. It can go badly wrong. Try re-loading the page.
There's some combination of shift and alt when you press the refresh button that should bypass the cache. Instead of going to ukcaving.com, put "?rhubarb" at the end without quotes. The cache won't know what to do, so it will connect you directly to ukcaving.com which will ignore the extra junk. Worth a try anyway, at least you may get an idea of where the problem is.