-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content Security Policy Frame Ancestors builder doesn't allow multiple URIs in single call #178
Comments
`AddFrameAncestors()` derives from `CspDirectiveBuilderBase` rather than `CspDirectiveBuilder`, so the normal extensions don't apply Fixes #178
Hey @JackGilmore, yeah this is just a quirk - the |
`AddFrameAncestors()` derives from `CspDirectiveBuilderBase` rather than `CspDirectiveBuilder`, so the normal extensions don't apply Fixes #178
Awesome! Thanks for turning this around so quickly :) Would it be possible for you to publish a new version of your nuget package so I can pull this down to use with my app? |
Just pushed out a new version which contains this, v0.24.0! |
When using
CspBuilder
during callingAddContentSecurityPolicy()
for creating aHeaderPolicyCollection
, the builder allows you to pass in anIEnumerable<string>
with multiple URIs e.g.This doesn't seem to be the case as the
.From()
method forAddFrameAncestors()
only appears to support a single string URI e.g.Is this an intentional design or is it possible to make
AddFrameAncestors().From()
support anIEnumerable<string>
also?The text was updated successfully, but these errors were encountered: