Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Jun 11, 2020

Issue #, if available:

Description of changes:

  • Create edge lambda to set security-related headers on the CloudFront distro
  • Two other unrelated fixes:
    • Fix a type error when leaving the APIs page
    • Bust cache so the API properly loads in the APIs page after immediately enabling it in the admin panel

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ghost ghost changed the title Set security headers on CFN responses Set security headers on CloudFront responses Jun 11, 2020
@ghost ghost force-pushed the set-security-headers branch 2 times, most recently from 96b5bc1 to 1d75724 Compare June 19, 2020 20:26
amazon-meaisiah added 8 commits June 19, 2020 19:48
This could be necessary in the future, so I want to lay the groundwork
now. Also, it's a potentially common need in development.
Swagger UI doesn't offer any facilities to clean up after itself, so we
have to tolerate it.
When starting from scratch, if you go to the admin panel, set the first
API to display, and switch back to the APIs page, it's now out of date
with what's server-side.
@ghost ghost force-pushed the set-security-headers branch from 1d75724 to 2191174 Compare June 22, 2020 18:23
@ghost ghost marked this pull request as ready for review June 22, 2020 18:33
@ghost
Copy link
Author

ghost commented Jun 22, 2020

@ghost ghost merged commit a1f1642 into staging Jun 22, 2020
@ghost ghost deleted the set-security-headers branch June 22, 2020 20:40
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants