[allura:tickets] #7971 Incorrect Content-Type on first CSS requests, causing CSS not to be used

[Dave Brondsema <da...@brondsema.net>]

- **labels**: ux, getting-started, sf-2, sf-current --> ux, getting-started, sf-2
- **status**: open --> closed
- **Comment**:

I've removed the hidden CSS mimetime notice and cache clearing recommendation.  We want to know if this happens any more.  If it does, we can reopen a ticket.



---

** [tickets:#7971] Incorrect Content-Type on first CSS requests, causing CSS not to be used**

**Status:** closed
**Milestone:** unreleased
**Labels:** ux getting-started sf-2 
**Created:** Tue Aug 18, 2015 03:52 PM UTC by Dave Brondsema
**Last Updated:** Wed Sep 23, 2015 03:58 PM UTC
**Owner:** nobody


I can't pull up an example right now unfortunately since it's only occasional.  I think the URLs are the ones with `_ew_` in the path.

And then if the response gets cached, then subsequent page loads still don't work either.

[#7028] was for the same issue, so see that for additional details.  That ticket just resulted in a workaround, but its not great (especially if it gets cached).  This ticket is for a real fix.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.