Setting forward headers in CloudFront

[Floriferous]

The README part about adding forward headers are not clear enough for CloudFront.

According to what I could find here: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/forward-custom-headers.html#forward-custom-headers-configure

It seems that the way to add forward headers is by doing this in the Origin Settings:

It's not totally clear that the value fields should remain empty though. So far I haven't been able to make this package work. How do you test a CDN on localhost?

There is no setting called Forward Headers, as mentioned in the README, I therefore can't set the setting to whitelist..?

[sabativi]

Hey @Floriferous did you manage to make things work with CloudFront ?

[Floriferous]

Never got it to work sadly, no.

[sabativi]

For info, this was the setting that I was missing

[manueltimita]

For info, this was the setting that I was missing

If you tick "Use legacy cache settings" you should have access to the Whitelist Headers group. Here's the full list of headers to be whitelisted (use Add Custom for headers not found in the multiselect list):

Access-Control-Allow-Origin
Content-Security-Policy
Origin
Strict-Transport-Security

PS. In my case this package did not add the header Access-Control-Allow-Origin * to the fonts. You have an option to set it like specified in the Meteor docs. Or for NGINX, this is from Josh Owens:

    location ~* .(eot|ttf|woff)$ {
        root /opt/crater/app/programs/web.browser; # CHANGE /opt/crater/app to whatever the location of your meteor bundle is
        access_log off;
        add_header Access-Control-Allow-Origin *;
        add_header Vary Origin;
        add_header Pragma public;
        add_header Cache-Control "public";
        expires max;
    }

CC @Floriferous @sabativi