[wp-hackers] Plugin conflicts with latest version of Jetpack

[Bryan Petty]

On Wed, Jan 2, 2013 at 10:45 AM, Mike Schinkel <mike at newclarity.net> wrote:
> Given the setup which is pretty similar to a lot of shared hosting wouldn't you expect similar for most WordPress installs?  My understanding is the server needs to be configured explicitly to serve Expires headers for static content which is something that most WordPress users are unlikely to have done.  Or am I missing something or misunderstanding?

Bluehost uses servers configured to use ETags, and as such, this is
the behavior seen there (at no point are Expires headers even used):

On subsequent page load (no refresh): Static assets served from
browser cache, no server request made (just as Otto describes).
On soft refresh (F5, or clicking Reload): Server request made, but if
still cached, this will still result in 304.
On hard refresh (Ctrl-Reload): Full CSS file returned from server and
re-cached by browser.

At least, this is Chrome's behavior, other browsers may be different.
GoDaddy also uses ETags with the same behavior.

Regards,
Bryan Petty