autoref

5 ms·

1. 1.▲
   Protocol-Relative URLs to Fix Mixed-Content Warnings(autoref.com)

   41 points by autoref 14y ago|24 comments
2. 2.▲
   by autoref 14y ago

   Solution: use protocol-relative URLs now http://autoref.com/blog/2012/09/13/the-tech-behind-autoref-p...
3. 3.▲
   by autoref 14y ago

   This isn't recommended since many browsers and proxies do not cache resources that are referenced using a query string, even if a cache-control or expires header is set appropriately. Google says Squid up to 3.0 will not do so: https://dev
4. 4.▲
   by autoref 14y ago

   The bad part is no file is cached between pushes, right?
5. 5.▲
   by autoref 14y ago

   An excellent point, but you have to consider warm cache vs cold cache optimizations. For a cold cache, it's better to combine assets and reduce HTTP requests. We do that on our homepage. For a warm cache, it's better to split assets up so t
6. 6.▲
   by autoref 14y ago

   Right. Images and fonts have to be written and hashed first, then used in the template rendering of the CSS file. The CSS references the assets with hashes in the filenames.
7. 7.▲
   Static Asset Compilation(autoref.com)

   48 points by autoref 14y ago|39 comments