Conversation
Member
Author
|
Current-feedback closeout (2026-07-26):
No follow-up commit was necessary, and draft/admin state was left unchanged. |
niemyjski
force-pushed
the
feature/strict-dynamic-csp
branch
from
July 30, 2026 18:18
0bddf5a to
7ee01eb
Compare
niemyjski
force-pushed
the
feature/strict-dynamic-csp
branch
2 times, most recently
from
July 30, 2026 19:39
b7eab28 to
3cb0aa3
Compare
Member
Author
|
Fixed the failing CSP fallback integration coverage in Verification after push:
Re-audited the review surfaces: there are no submitted reviews or review threads to resolve. |
niemyjski
force-pushed
the
feature/strict-dynamic-csp
branch
from
September 16, 2026 00:32
8e10da9 to
f8d1597
Compare
|
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
1 participant
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.
Summary
Serve frontend HTML with a fresh 32-byte nonce and a strict script CSP, without
unsafe-inlineorunsafe-eval. The existing ASP.NET response pipeline stamps scripts, disables HTML caching, and prevents conditional or range requests from returning a body with a mismatched nonce. API responses and MCP streaming bypass the transformation.Use the same tested policy in production and the development frontends. Remove the unused SPA file-reading middleware, keep Angular object rendering compatible with CSP, and configure Svelte's Zod validation to avoid runtime code generation.
Verification
mainatbb0315556.npm run validate, production build, and 13 CSP tests passed.Shared service tests and authenticated/provider flows were not run locally. Scalar rendered, but its bundled code still reported a caught eval probe and blocked external font/registry requests; this is not a claim of complete Scalar or provider compatibility.
Breaking changes
No API route, response schema, authorization, or configuration changes. Frontend scripts now require a valid nonce or a trusted loader; inline styles remain allowed.