"Prefetching is not allowed due to the various privacy issues that arise."

prisonermonkeys

Be Fearless
Premium
33,155
Peru
Hammerhead Garage
Sometimes when I click the All Forums link at the top of the page, or come into the site via Google, I get a blank page that says "Prefetching is not allowed due to the various privacy issues that arise." What does this mean, and what am I doing wrong?
 
What browser and operating system are you using? Are you using plugins such as Fasterfox or have you installed the Google Toolbar?
 
What type of Internet connection are you using? Is there any chance you're accessing the site through a proxy server or some other type of filtering software?
 
Yeah, I'm on the university network. That probably explains it - I'm running through a wireless connection, as there's been some problems with the network. Honestly, I have no idea what my settings are and I'm hestitant to touch them because I've had a lot of work done to them. The university upgraded its network for this year, and because my computer wouldn't take to the new settings, the IT building had to come up with a series of increasingly-creative solutions just to get me on the network. As a result, they learned a lot about it, but they changed a lot and I have no idea what they did, much less the consequences of undoing it.

That said, the prefetching thing isn't much of an issue, for me at least - a forced refresh with Ctrl + F5 takes me into the forums.
 
Unfortunately, that's probably the source of the problem. Some foolishly-configured (they probably have their reason, though I'd say it's more trouble than it's worth on today's web) proxy servers on large networks will attempt to "prefetch" web pages which are linked from the page you're currently viewing. On "normal", static pages, this can speed things up, but it can cause problems on dynamic sites that change content (like our forums) each time you request them. It looks like our forum software, vBulletin, is detecting the proxy's pre-fetching activity and is protecting itself from undue load.

I haven't seen this issue before, and I don't know how to fix it (or if that would even be a good idea in the first place). For now, I think your CTRL+F5 solution is for the best.
 
Back