Skip to content

fix(api): keep the stored CSP when a share is updated - #54

Merged
ernolf merged 1 commit into
mainfrom
ernolf/fix/preserve-csp-on-share-update
Aug 18, 2026
Merged

fix(api): keep the stored CSP when a share is updated#54
ernolf merged 1 commit into
mainfrom
ernolf/fix/preserve-csp-on-share-update

Conversation

@ernolf

@ernolf ernolf commented Aug 18, 2026

Copy link
Copy Markdown
Owner
  • Core's "Update share" posts only enabled and rawOnly, so set() wrote NULL over the per-share CSP for members of the CSP editor group
  • Treat an absent csp parameter as unchanged and fall back to the stored value, the way the non-editor branch already did
  • An explicitly sent empty string still clears the CSP

Fixes #53

- Core's "Update share" posts only enabled and rawOnly, so set() wrote NULL over the per-share CSP for members of the CSP editor group
- Treat an absent csp parameter as unchanged and fall back to the stored value, the way the non-editor branch already did
- An explicitly sent empty string still clears the CSP

Signed-off-by: ernolf <raphael.gradenwitz@googlemail.com>
@ernolf
ernolf merged commit 3f2a063 into main Aug 18, 2026
45 checks passed
@github-actions
github-actions Bot deleted the ernolf/fix/preserve-csp-on-share-update branch August 18, 2026 23:00
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.

Per-share CSP (Edit CSP) is saved but never delivered — the default fallback CSP is always served

1 participant