docs: document opt-in safeUrlSchemes configuration parameter (CP: 25.1)#5790
Open
mcollovati wants to merge 1 commit into
Open
docs: document opt-in safeUrlSchemes configuration parameter (CP: 25.1)#5790mcollovati wants to merge 1 commit into
mcollovati wants to merge 1 commit into
Conversation
Flow 25.1 adds URL scheme validation for `Anchor.setHref()`, `IFrame.setSrc()` and `Page.open()`, but the validation is opt-in: URLs of any scheme are accepted unless the `safeUrlSchemes` parameter is set. Document the `safeUrlSchemes` parameter and the Unsafe URL Schemes security topic, and note that the default flips to enabled in Vaadin 25.2 so users are aware of the change when migrating. Part of vaadin/flow#24924
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.
Backport of #5775 to the
v25.1branch, adapted for the Flow 25.1 backport vaadin/flow#24924.Two differences from the
mainversion:safeUrlSchemesparameter defaults to*, so every URL scheme is accepted unless the parameter is set. The docs describe how to enable it rather than how to relax an already-enabled default.com.vaadin.safeUrlSchemeslegacy name. The 25.1 backport only recognizessafeUrlSchemes, so the deprecated-alias note is omitted.Also adds a note that the default flips to enabled in Vaadin 25.2, so users are aware of the behavior change when migrating.
The
upgrading/index.adocchange from #5775 is intentionally omitted: it documents a breaking change in 25.2, which doesn't apply to the opt-in 25.1 backport.Part of vaadin/flow#24924
🤖 Generated with Claude Code