304 support broken under SSL?

[matt]

I was doing some investigating on why the admin section of WP.com was feeling slow, and one thing I noticed is that none of the scripts or anything else called ever returned a 304 not modified. I played around with sending various combinations of last-modified headers and etags, and I could never get it to return a 304. Here's an example:

https://wordpress.com/wp-includes/js/scriptaculous/controls.js

If I go to the same URL without HTTPS, I get a 304 on reload:

http://wordpress.com/wp-includes/js/scriptaculous/controls.js

We're on 2.2. Is this something that is specific to SSL, something in our setup, or could it be a bug in LSWS?

 

[mistwang]

It is not likely a LSWS bug, as SSL transport layer has nothing to do with 304 support.
As I knew, some browsers do not cache any content received under SSL, some browsers do.
Tried those URLs under firefox with "Live HTTP headers" add-on, 304 has been returned.

 

[matt]

Odd, I'm using Firefox's live headers too.

 

[xing]

Throwing in a 3rd Firefox 1.5.0.6 + Live Header test.

From my end, the ssl url also returns 304 not-modified on re-load.

 

[matt]

I don't know what to say, it's working fine now. I'll see if I can reproduce it consistently again. Thanks for the sanity check.