-
Notifications
You must be signed in to change notification settings - Fork 58
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
CSP violations when using AutoCompleteTextField #347
Comments
Hi Anna, I also tried strict CSP some times ago and that does not work with
templates. I didn't see any workaround for this, the templates have to be
in a script tag... Maybe it changed since. any help with the
investigation would be appreciated...
… |
Hi @sebfz1 , thanks for confirming. I believe we could be more compliant here by using our own |
Thanks Anna, that's interesting!
I will try to give it a try, but I'm probably not available before at least
2 weeks... If you want to try it out and submit a PR, you are also
very welcome! :)
|
I will give it a try this week |
I also use CSP-NONCE and had to .add(CSPDirective.SCRIPT_SRC, CSPDirectiveSrcValue.SELF) to make it work |
While it might work, it does not comply with a stricter CSP policy. Check the policy for example in https://csp-evaluator.withgoogle.com/:` "'self' can be problematic if you host JSONP, Angular or user uploaded files." |
We are currently in the process of introducing a strict CSP policy for script src (CspSettings ->
add(SCRIPT_SRC, NONCE)
as was introduced with Wicket 9.In our codebase we have some components making use of
AutoCompleteTextField
. Browser (Firefox, 101.0.1) is reporting CSP violations and templates are no longer working as a result of enforcing the strict policy for scripts.For example:
The text was updated successfully, but these errors were encountered: