Search results

See, the thing is that 412's aren't really cache response codes. The 400s are generally certain types of errors, like 404. Cache response codes should be 304 if it's coming from the server (or something even "200 from cache" if the browser doesn't even want to check the server).

At your service, m'lady *sweeps a bow*

HHmm... looks like it's crapping out on the If-None-Math / ETag or If-Modified-Since / Last-Modified-Date headers... the "If-Modified-Since" precondition isn't met (and the If-None-Match isn't either), so the 412 is sent. Looks like that's all fine according to HTTP spec, and seems that it's the...

I am so glad you guys know what you are doing to some extent :lol

Holy crap - that's weird. I've never seen a 412 response code before :blink. Based on my research, it's something that the server can respond with when the client send a precondition header - and I don't think vBulletin does any of that anyways. This sounds like a server side issue... But first...

Nope nope, but if he's adept, open dev tools (F12) and inspect the source where the images should be. It'll give a <img> tag (or some other tag perhaps). Chrome dev tools should let you grab that src URL and then you can put that into another tab. If you get it then, reload the original page and...

I'd have to see it reproduced myself to be sure, or remote into someone's computer who is getting it. It's most likely client side from what I can tell so far, but if more people report the same thing recently, maybe we're having bandwidth issues at some level :cheese. How long has this been...

Try to clear cache / force refresh. Not sure on the iPad, but if you go to settings, Safari... and something like clear or delete cache / temporary files, that should do it.