9522 2016-04-26 13:47:04 +0000 Documentation isn't cachable 2018-11-09 15:56:48 +0000 1 1 5 Infrastructure Website web-structure unspecified All Multiple RESOLVED FIXED Medium normal Future 1 ross.burton mhalstead jefro mhalstead sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 61689 0 ross.burton 2016-04-26 13:47:04 +0000 The documentation, for example http://www.yoctoproject.org/docs/2.0.1/mega-manual/mega-manual.html, isn't cachable by either Chrome or Safari on my laptop. Network tracing shows that whilst all the content - the images, stylesheet and so on - are all HTTP 304'd so the local cache is used, mega-manual.html is always returned entirely instead of being cached. 62158 1 mhalstead 2016-05-12 17:20:42 +0000 We add Google Analytics during page generation for all of the .html files in the documentation. This updates the last-modified header and prevents the response from being cached. There are a few ways to fix it: rebuild the webserver to support keeping the last-modified header static add the GA code to the static doc files after they are generated stop tracking how our docs are accessed I'll pursue the first option since we don't lose anything and I don't interfere with Scott's workflow that way. 74414 2 jefro 2017-06-20 21:23:14 +0000 we are making changes to the website - wanted to make sure to watch this to make sure we implement it in the new world order 82130 3 mhalstead 2018-11-09 15:56:48 +0000 This was resolved by the web server moves in March. Seeing 304 for the main manual now and "200 OK (from memory cache)" for the other assets.