{"action":"opened","issue":{"url":"https://api.github.com/repos/laurilehmijoki/s3_website/issues/208","labels_url":"https://api.github.com/repos/laurilehmijoki/s3_website/issues/208/labels{/name}","comments_url":"https://api.github.com/repos/laurilehmijoki/s3_website/issues/208/comments","events_url":"https://api.github.com/repos/laurilehmijoki/s3_website/issues/208/events","html_url":"https://github.com/laurilehmijoki/s3_website/issues/208","id":130542080,"number":208,"title":"`no-cache; max-age=0` vs `no-cache, max-age=0`","user":{"login":"pjanik","id":767857,"avatar_url":"https://avatars.githubusercontent.com/u/767857?v=3","gravatar_id":"","url":"https://api.github.com/users/pjanik","html_url":"https://github.com/pjanik","followers_url":"https://api.github.com/users/pjanik/followers","following_url":"https://api.github.com/users/pjanik/following{/other_user}","gists_url":"https://api.github.com/users/pjanik/gists{/gist_id}","starred_url":"https://api.github.com/users/pjanik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pjanik/subscriptions","organizations_url":"https://api.github.com/users/pjanik/orgs","repos_url":"https://api.github.com/users/pjanik/repos","events_url":"https://api.github.com/users/pjanik/events{/privacy}","received_events_url":"https://api.github.com/users/pjanik/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-02-02T01:43:03Z","updated_at":"2016-02-02T01:43:03Z","closed_at":null,"body":"CloudFront doesn't want to update my files, even though I've set max-age to 0 in s3_webiste config.\r\nFiles uploaded by old version of s3_website work as expected. I've noticed that that files uploaded by the latest version use `no-cache; max-age=0` header while old version was setting `no-cache, max-age=0`.\r\nNot sure about correct and/or accepted format (would need to dig into some specs), but comma seems to be widely used. I haven't found examples with semi-colon. \r\nNot sure, but maybe CloudFront gets confused and uses default TTL instead of max-age value?\r\nAnyone experiencing similar issues or able to replicate it?"}}