unusual test results

Web Performance Discuss Test Results
1

hi

i have two websites both use cloudfront, however the tests are very different

on one tests it states no expires or cache for cloud items, the other website states all is OK

however both have the same cache and expires set in the meta on cloudfront

thanks

2

Are you compressing stuff? I think cloudfront requires http_version 1.0, not 1.1.

3

yes gzip is on server, both sites are on same dedicated server, i am beginning to think webpagetest does not understand when both expires and max-age are specified on each file on cloudfront ?? doing the test again it changes the results for the same files.

4

Do you have a link to a good and bad test result? The full set of headers should be available for inspecting in the result and if there’s a bug I’d like to fix it.

5

unfortunately not, but I will do the two tests again tmrw and post them here :slight_smile:

thanks

6

hi
this is test 1
http://www.webpagetest.org/performance_optimization.php?test=130521_XQ_D8P&run=1&cached=0
notice FAILED - (No max-age or expires) - http://d2wvmac51oegod.cloudfront.net/pattern_images/yukon.jpg
this has max age and expires set in cloud
test 2
http://www.webpagetest.org/performance_optimization.php?test=130521_1E_D78&run=1&cached=0
notice there is no issues with cloud

thanks

7

Thanks, definitely looks like a bug (must be a strange one to be so selective). I opened a critical bug to track it and should have something in the next couple of days: Google Code Archive - Long-term storage for Google Code Project Hosting.

8

Ahh, think I figured it out. The cloud responses are serving a Date header which is in the past and the cache-control expiration is relative to that date:

Date: Wed, 24 Apr 2013 16:57:07 GMT
Cache-Control: max-age=1128800
Last-Modified: Wed, 24 Apr 2013 15:58:45 GMT

I’m guessing that you don’t actually want that Date header being served statically.

9

btw, that was from a test I just ran (on May 29th).

10

thanks for reply

what do you suggest ?

thanks

11

I suggest fixing the Date header. If you have it statically defined then remove it.

12

yes it is defined in amazon S3, so probably best then using either max-age or date but not both then

thanks