1) The last section of the README.md is updating-the-site-content-security-policy. This refers to a file, source/secured-headers/index.js, that no longer exists as of pull-request #42. This pull request removed the lambda@edge function for security headers and replaced it with the more modern Cloudfront response headers.
2) I've already submitted feedback, but the Cloudfront developer guide still mentions lambda@edge in the "Getting started with a secure static website" example even though this github project no longer uses lambda@edge.
Would it be OK if I take a crack at submitting a pull request for the README?
ConnorKirk
commented
4 months ago
Two things about content-security-policy:
1) The last section of the README.md is updating-the-site-content-security-policy. This refers to a file, source/secured-headers/index.js, that no longer exists as of pull-request #42. This pull request removed the lambda@edge function for security headers and replaced it with the more modern Cloudfront response headers.
2) I've already submitted feedback, but the Cloudfront developer guide still mentions lambda@edge in the "Getting started with a secure static website" example even though this github project no longer uses lambda@edge.
Would it be OK if I take a crack at submitting a pull request for the README?