Back in March 2017, Google added a new feature to Chrome to prevent XSS attacks. Unfortunately, it wasn't well tested, and it caused havoc with vBulletin forums.
Specifically, if your post or PM has a reference to another thread in the same forum, when you "Preview Post" or "Preview Message", Chrome raises the entirely misleading and highly frustrating error:
(I got the same error when trying to post this message because of the link below.)This page isn’t working
Chrome detected unusual code on this page and blocked it to protect your personal information (for example, passwords, phone numbers and credit cards).
As you probably know, Google is highly unresponsive to bug reports, and has marked the bug report on its own site as "won't fix".
The solution (which is really a workaround) is:
I raised this back then, and reported a bug as requested, but it's over a year later and this problem still hits. It gives a bad impression to Chrome users, who think that the fault lies with Ubuntu Forums and not Google.Please add this HTTP Header Field: x-xss-protection: 0
Details: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
Could this issue be raised a level, please?
Bookmarks