-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
GH-45720: [Docs] Kapa.ai widget not loading on the dev docs #45764
base: main
Are you sure you want to change the base?
Conversation
|
Hmm, looking at the original error, I'm now wondering if I need to add the others back in to prevent blocking access to others?
|
I think this is wrong actually - I may need to open a ticket with infra... |
Or just update the .htaccess file on the arrow-site repo... |
@ianmcook may know the Content-Security-Policy settings because Ian worked on it such as apache/arrow-site#603 recently. |
AIUI, the only way to modify the CSP is to ask privacy@apache.org. See https://infra.apache.org/csp.html for details. I banged my head on the wall for several days trying to get the GitHub star count badge to work by modifying the CSP here using meta tags and then using |
Thanks both, I was going round in circles a bit there; I will drop them an email! |
It sounds like they are setting a very high bar for adding any new sites to the CSP allowlist. May the odds be ever in your favor :) |
I'm hopeful - it's one of the few things expressly allowed as kapa.ai has signed a DPA with the ASF, so it feels like it's just the technical details to resolve here 🤞 |
Rationale for this change
Add the kapa.ai domain to the content security policy so that the AI bot we are trying out can load. Following the approach shown on apache/dubbo-website#2925 but being more restrictive on URLs.
What changes are included in this PR?
Updates to sphinx and pkgdown docs to fix this
Are these changes tested?
Nope - this wasn't an issue on the docs built in crossbow when I tested it on the PR, so I was thinking I just check it's working on the dev docs once they're built
Are there any user-facing changes?
Nope