Misinterpretation by Audits (Developer Tools) cache-control: max-age = 31536000, public
Reported by
d...@indiamart.com,
Jun 26 2018
|
||||
Issue descriptionIf the cache-control response header has space before and after = (equal) for max-age value pair, then in that case the Chrome Audits marks it as "Uses inefficient cache policy on static assets". In that case it shows "Cache TTL" to be none, despite having response header as "cache-control: max-age = 31536000, public". What steps will reproduce the problem? (1) Visit https://dir.indiamart.com/impcat/floral-printed-kurti.html (2) Go to Audits tab in Developer Tools and Perform an Audit. (3) Check the Diagnostics section. for different images. What is the expected output? It should not list these images with "max-age = 31536000" under "inefficient cache policy". What do you see instead? Shows "Uses inefficient cache policy on static assets" with "Cache TTL" none.
,
Jun 26 2018
,
Jun 27 2018
,
Jun 27 2018
Can reproduce. However this is tracked in another bug tracker for lighthouse. Opened an issue there: https://github.com/GoogleChrome/lighthouse/issues/5572
,
Jun 27 2018
Thanks for refiling over in GitHub @dtapuska! FYI ds@indiamart.com, this is WAI per the spec (https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). Whitespace is not allowed between the directive/equals sign/seconds.
,
Jun 28 2018
Thanks a lot. But, I notice that the Chrome Browser (v67.0.3396.87 as well as v68.0.3440.42) do honor the Cache-Control with spaces before and after the equal sign for Max-Age directive and value in seconds. In that case the LH Audit tool too should follow the same (else the audit results are not matching with real behavior). |
||||
►
Sign in to add a comment |
||||
Comment 1 by jrobbins@chromium.org
, Jun 26 2018