mozilla/browserid — Issue #1141: Static resources should not generate 304s in server logs
Author: ozten
Created: 2012-02-16 21:35:19+00:00
State: open

With Issue 620, we've improved our caching for static assets.

Unfortunately, UA still check to see if a resource is up to date, generating a 304 response.

per @lloyd - for js/css resources, don't sent ETag or Last-Modified (should fix upstream)

Actual: /produciton/en-US/dialog.js 304 in firebug / node server logs

Expected: No HTTP traffic for this resource after first 200 request.