Repository navigation
fix(security): follow OWASP's moved Secure Headers URL and correct two source labels - #314
Merged
Merged
Conversation
…o source labels - clear-site-data, x-content-type-options: owasp.org/www-project-secure-headers/ now reaches the page only after three 308s; cite the final URL. - referrer-policy: TR/referrer-policy is a Candidate Recommendation, not an Editor's Draft; the web.dev source is 'Referer and Referrer-Policy best practices', not 'A new default Referrer-Policy for Chrome'. - permissions-policy: the source labelled web.dev is on Chrome for Developers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
6d57da4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://20c31987.specification-website.pages.dev |
| Branch Preview URL: | https://scan-2026-11-11-security-cit.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Daily standards scan, 2026-11-11. The rotating citation slice was security (25 pages, 74 URLs). I checked the HTTP status, final URL and page
<title>for each one against the citation's label.What changed
https://owasp.org/www-project-secure-headers/now gets to the page only after three 308 redirects. Both pages now cite the final URL,https://owasp.org/projects/secure-headers-project.TR/referrer-policy/was labelled "W3C Editor's Draft", but it is the W3C Candidate Recommendation of 26 January 2017, so it is now labelled that way. The web.dev source was labelled "A new default Referrer-Policy for Chrome", but the page at that URL is "Referer and Referrer-Policy best practices", so the label now uses that title.These are label and URL fixes only. No claims, statuses or
updateddates change, so there's no changelog entry.Checked, no change needed
rfc-editor.org/rfc/N→/info/rfcN/redirects are expected, and the URLs we cite are still the right ones.w3.org/TR/*pages return 403 to curl. I read them with WebFetch instead, and the labels on CSP3, Fetch Metadata, Permissions Policy, Trusted Types, SRI and Clear Site Data (all Working Drafts), Mixed Content (CRD) and WebAuthn L3 (REC, 25 Aug 2026) all match.npm run buildpasses. I didn't redeploy the MCP Worker; that happens through the Action after merge.🤖 Generated with Claude Code