![]() |
"No max-age or expires" for images that already have expire headers - Printable Version +- WebPagetest Forums (https://www.webpagetest.org/forums) +-- Forum: Web Performance (/forumdisplay.php?fid=3) +--- Forum: Discuss Test Results (/forumdisplay.php?fid=4) +--- Thread: "No max-age or expires" for images that already have expire headers (/showthread.php?tid=14224) |
"No max-age or expires" for images that already have expire headers - bundaumamtom1989 - 02-26-2016 01:53 PM This is my test result: http://www.webpagetest.org/result/160226_RD_6JG/1/performance_optimization/#cache_static_content There are several images that are flagged as "No max-age or expires" for example this one: Code: FAILED - (No max-age or expires) - http://image.ttg-static.net/izaya-kankin-durarara-arabic-yamato-asaisai_45097774b31a4eaba6800a1baccba347.jpg However, when I inspect the headers, both the max-age and expires headers are available, for example, this is the result for url http://image.ttg-static.net/izaya-kankin-durarara-arabic-yamato-asaisai_45097774b31a4eaba6800a1baccba347.jpg using online tool http://www.webconfs.com/http-header-check.php: Code: HTTP/1.1 200 OK => This photo is stored in S3 server by Cloudfront and then shielded by Cloudflare, so the requests looks like this Quote:user browser -------> Cloudflare -------> Cloudfront -------> S3 I also read the question carefully from the thread http://www.webpagetest.org/forums/showthread.php?tid=14209 but it seems to be a diffrent problem. Please help! |