- [x] PR submitted against the `main` branch of `next-build`.
- [x] Link to the issue that this PR addresses (if applicable).
- [x] Define all changes in your PR and note any changes that could potentially be breaking changes.
- [x] PR includes steps to test your changes and links to these changes in the Tugboat preview (if applicable).
- [x] Provided before and after screenshots of your changes (if applicable).
- [x] Alerted the #accelerated-publishing Slack channel to request a PR review.
- [ ] You understand that once approved, you are responsible for merging your changes into `main`. (Note that changes to `main` will move automatically into production.)
Confirm in the response headers that you are seeing Next Build content.
Confirm that you do not see any errors in the console indicating that Content Security Policy is preventing scripts from loading.
Confirm that the page is loading fully as expected, including the header & footer.
View source (not with the web inspector; actual source), and search for ssgManifest.js. For the script tag where that is loaded, you should see a nonce included in the script tag, something like the following:
Description
Adds nonce placeholders which will be substituted by the reverse proxy.
Ticket
https://github.com/department-of-veterans-affairs/next-build/issues/789
Developer Task
Testing Steps
You will need to set up a reverse proxy Preview server tunnel, using the preview instance from this PR: https://github.com/department-of-veterans-affairs/vsp-platform-revproxy/pull/687
Confirm that a Staging Content release has gone out with this code:
tcosgrove_nonce
selected rather thanmain
: https://github.com/department-of-veterans-affairs/next-build/actions/workflows/content-release-staging.ymlThen, run through these steps:
ssgManifest.js
. For the script tag where that is loaded, you should see a nonce included in the script tag, something like the following:Do the above steps again for any individual event page.