You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2014/07/10 17:10:08 UTC
[allura:tickets] #7027 Cache /nf/tool_icon_css better
- **status**: code-review --> in-progress
- **Comment**:
Is there some missing code related to the new `file_expires_header_secs` config? I'm not seeing anything that uses that to set the `Expires` value header further out.
---
** [tickets:#7027] Cache /nf/tool_icon_css better**
**Status:** in-progress
**Milestone:** forge-jul-11
**Labels:** performance bitesize
**Created:** Mon Jan 06, 2014 08:57 PM UTC by Dave Brondsema
**Last Updated:** Sun Jun 29, 2014 02:59 AM UTC
**Owner:** Tim Van Steenburgh
/nf/tool_icon_css is a dynamically created CSS file. It is currently cached via etag headers, but that means a request still goes to the server and it has to respond with a 304. So this is a lot of extra requests (on sf.net, ~35% of /nf/tool_icon_css requests are 304s)
We should set a future expires header, and then do cache-busting with a unique URL by appending `?{{config.build_key}}` (build_key is already used for this purpose for all our other static resources)
---
Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.