Problem
In recent Chrome browser, it has become little annoying to work with SharePoint tool due to Chrome throwing ERR_BLOCKED_BY_XSS_AUDITOR error when working with the Script Editor web part. This is due to XSS auditor on Chrome blocking JavaScript included in the Script Editor Web Part. Issue occurs on SharePoint Online and on-premises SharePoint 2016 and 2013 and occurs regardless if site is accessed via HTTP or HTTPS.Steps to repro:
- On SharePoint publishing page, add Script Editor web part to content area or web part zone
- Add the following code to the web part (any JS will do the trick):
<script>
console.log("asd")
</script>
- Click Insert at the bottom of the Script Editor content dialog
--> Chrome throws you to page saying
This page isn’t working
- Try visiting the site's homepage.
Workaround
You can disable the XSS Auditor by appending the following value to web.config on your on-premises SharePoint 2013 or 2016 web site.<system.webServer>
<httpProtocol>
<customHeaders>
<add name="X-XSS-Protection" value="0" />
</customHeaders>
For SharePoint Online, there is no workaround at the moment.
d
ReplyDeleteOK, I am not using Share point. . . I am attempting to edit the listings in my online store at an auction site.
ReplyDeleteHow do I correct this problem?
You would need to contact the auction site host and ask them to add similar header option on their servers.
Deleteexcellent my friend, I tried and function perfect!
ReplyDeleteSharePoint 2013 server, Standard Edition
Thank you...
This workaround of course does not work with SharePoint Online.
ReplyDeletehttps://www.bmyers.com/public/Bypassing-the-XSS-AUDITOR-error-in-Chrome.cfm
DeleteThis works for SharePoint Online, no server-side modifications needed: http://softlanding.ca/blog/working-past-script-editor-webpart-error-in-sharepoint-on-google-chrome-(2)
DeleteWorkaround - Shortcut = "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -disable-xss-auditor . But this solution is not practical..
ReplyDeleteSharePoint Online workaround here: http://softlanding.ca/blog/working-past-script-editor-webpart-error-in-sharepoint-on-google-chrome-(2)
ReplyDeleteThat is a whole lot more practical than asking admins to add code to the web.config that will be wiped out by the next SharePoint update. Just sayin :)
ReplyDelete