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
Refused to execute script #4
Comments
Thanks for reaching out! Please make sure you:
Once you redeployed after enabling the feature, the route |
I redeployed but still the same error |
@chriswdmr I'm getting the same error even after deployment. I'm using the following versions: "@vercel/analytics": "0.1.3",
"next": "12.1.4", Can you please re-open this issue? |
I still have this error too but I don’t have the permission to reopen it sorry |
@ghoshnirmalya can you please share a deployment URL with us? When was your last redeployment? @alex289 I see your production deployment already exposes |
I did not check if it was resolved after this but if it is I can say it's resolved for me |
@tobiaslins You can check out https://rapidapi.com/guides/categories/graphql. The last deployment was 4 days ago. |
@ghoshnirmalya I can't see the deployment url (vercel.sh) easily because the /guides thing is proxied right? |
@ghoshnirmalya I just found out that you're proxying the Next.js app and the root is not |
@tobiaslins That is correct. |
@ghoshnirmalya Can you tell us more on your proxy setup? It seems like (https://rapidapi.com/guides/va/script.js) is also not available. Could you please send us a deployment url (ending with |
@tobiaslins You can use https://devrel-stack-guides.vercel.app/guides. |
I just added this to my site but when I visit it this error gets logged:
Refused to execute script from 'https://alexanderkonietzko-84q9dz1ke-alex289.vercel.app/va/script.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
Does this happen because I have X-Content-Type-Options: nosniff enabled?
Here is my repo for more information
The text was updated successfully, but these errors were encountered: