Skip to content

Conversation

@alxndrsn
Copy link
Contributor

@alxndrsn alxndrsn commented Nov 2, 2025

Closes #1403

What has been done to verify that this works as intended?

Fresh tests.

Why is this the best possible solution? Were any other approaches considered?

Simple. Open to alternatives, but couldn't think of any!

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

  • should reduce browser console noise
  • may override current script-src, in which case 'self' will need to be added. This will be noticed in testing, or in prod (where it would replace the current CSP violation with a new one, so not a big deal)

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

  • branched off and targeted the next branch OR only changed documentation/infrastructure (master is stable and used in production)
  • verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

@alxndrsn alxndrsn marked this pull request as ready for review November 2, 2025 11:24
@alxndrsn alxndrsn changed the title nginx: udpate CSP for frontend maps nginx: update CSP for frontend maps Nov 2, 2025
@matthew-white matthew-white requested review from brontolosone and removed request for matthew-white November 5, 2025 19:01
Copy link
Member

@matthew-white matthew-white left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is a small change, so I think I can go ahead and approve. 👍

@matthew-white matthew-white removed the request for review from brontolosone November 17, 2025 23:53
@matthew-white matthew-white linked an issue Nov 18, 2025 that may be closed by this pull request
@alxndrsn alxndrsn merged commit d833567 into getodk:next Nov 18, 2025
5 checks passed
@alxndrsn alxndrsn deleted the map-csp branch November 18, 2025 08:04
alxndrsn pushed a commit to alxndrsn/odk-central that referenced this pull request Dec 4, 2025
Split from https://github.com/getodk/central/pull/1526/files#r2587794987

The only identifiable Worker in frontend is from OpenLayers for displaying maps, and requires blob:, not data:.

Incorrect map-specific CSP introduced in getodk#1468.
alxndrsn pushed a commit to alxndrsn/odk-central that referenced this pull request Dec 4, 2025
Split from https://github.com/getodk/central/pull/1526/files#r2587794987

The only identifiable Worker in frontend is from OpenLayers for displaying maps, and requires blob:, not data:.

Incorrect map-specific CSP introduced in getodk#1468.
alxndrsn added a commit that referenced this pull request Dec 4, 2025
Split from https://github.com/getodk/central/pull/1526/files#r2587794987

The only identifiable Worker in frontend is from OpenLayers for displaying maps, and requires blob:, not data:.

Incorrect map-specific CSP introduced in #1468.

Co-authored-by: Hélène Martin <[email protected]>
Co-authored-by: alxndrsn <alxndrsn>
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.

Map violates Content Security Policy

2 participants