Azi al'Thone
Gaidin
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 client having such an issue. This is Chrome, correct? On a Mac or Windows?
I'm not sure that the 412 should be sent in this case, though... it seems that a cache response would be better. 412 seems to be more for web services to deny a request that doesn't match those versioning/modified timestamp conditions the prevent the request from executing, rather than to server cached content.
Herp derp, I'm sorry I don't have any answers right now. Google is lame on the issue as it relates to vB. I think what I may have to do is reproduce the error/bug by scripting a mock request like the one you sent me and then contact vB support.
Thanks for the info Dareth. Just to clarify, clearing cache does resolve this, right?
And also, no need for cookies. I don't know what the hell bb_password cookie is, but I doubt that it's the actual password hashed. The sessionid though should be kept private unless you were to log out and invalidate it.
I'm not sure that the 412 should be sent in this case, though... it seems that a cache response would be better. 412 seems to be more for web services to deny a request that doesn't match those versioning/modified timestamp conditions the prevent the request from executing, rather than to server cached content.
Herp derp, I'm sorry I don't have any answers right now. Google is lame on the issue as it relates to vB. I think what I may have to do is reproduce the error/bug by scripting a mock request like the one you sent me and then contact vB support.
Thanks for the info Dareth. Just to clarify, clearing cache does resolve this, right?
And also, no need for cookies. I don't know what the hell bb_password cookie is, but I doubt that it's the actual password hashed. The sessionid though should be kept private unless you were to log out and invalidate it.