Cache headers not being set on AWS

[thejuan]

Not sure if I set it up badly, but I'm not getting cache headers on my asset responses

content-encoding: gzip
content-type: application/javascript; charset=utf-8
date: Thu, 21 May 2020 01:20:13 GMT
last-modified: Thu, 21 May 2020 00:17:17 GMT
server: AmazonS3
status: 200
vary: Accept-Encoding
via: 1.1 cc3ab544aae38adfcc35bb790a813e46.cloudfront.net (CloudFront)
x-amz-cf-id: T3zX8wNNw9_T3awgXh7Q2kplZ9bhlhJqjKJIUOwQJpt0Ms8-1E1Ong==
x-amz-cf-pop: SYD4-C2
x-cache: Miss from cloudfront

Can view here https://register.hatch.exchange/?homecompany=domain

[evanderkoogh]

Looks like the header do not actually get set. I have created a PR to add those to the S3 objects in the deployer in #186

[thejuan]

Does CF pass through origin headers? Should this be set on the CloudFormation CF behaviour for assets path?

Edit
Most, no. :)

[geelen]

Pushed a new version of all packages, 1.0.0-rc.2.alpha.0, with this merged in. Can be accessed under the next tag, so pop that in your package.json manually or use npx fab@next init --version=next if you want to configure a new repo with the prerelease stuff.

[geelen]

Should hopefully get a proper RC2 out tomorrow btw

[thejuan]

Thanks, still blocked by #182 so can’t take this in yet.