What is XSS Auditor?
It's a built in chrome(and IE) 道具, switched on by default(you can 支配（する）／統制する it with X-XSS-保護 header, either 0;, 1; or 1;封鎖する), which 検査／視察するs all request params and 返答 団体／死体 trying to find if any of param 現在の as malicious script inside of 団体／死体. If it （悪事，秘密などを）発見するs anything 半端物 - by default it just 除去するs it from HTML. It can lead to weird things..
I am telling nothing new, but a trick from my previous 地位，任命する - slicing scripts and events you don't like in some page
You can 除去する any event "on*", any javascript:... link and any <script> tag. Best 的s: 確認するs(to make clickjacking easier) and framebuster scripts, sending them in request params(?除去=<script>remove_me();</script>). Without them life of hacker gets easier.
Don't touch my framebuster!
I created a neat trick to disallow such things to happen. Just put some 無作為の code in your code(<script src="framebuster.js?<%=ランド(1,9999)%>"></script>) - nobody knows how code looks in 返答 so it's impossible to '削減（する）' it off.
XSS Auditor is a 苦痛 in ass for scriptkiddies.
This is out of question. They just hate it. So let's use it even for greater good!
I wrote a デモ script which （悪事，秘密などを）発見するs if XSS Auditor 除去するd any 注入する and if it did - we 解雇する／砲火／射撃 up 文書.onxssprotection event(which will 通知する the 行政官／管理者 of website for example).
Don't touch my auditor of XSS Auditor!
And we don't want our XSS auditor 除去するd either - so when you use it be sure to 令状 src="auditor.js?RANDOM"
I like it more than any WAF - "native" 環境 （悪事，秘密などを）発見するs XSSes better than server 味方する middlewares(take into account 業績／成果 too).
This code is rather デモ and may content bugs, I did not 実験（する） it in all browsers and IE. Feel 解放する／自由な to 与える／捧げる.
I'd 選ぶ for Content-安全 政策 in 監視するing 方式 instead.
Reply削除するAgreed, if 報告（する）／憶測-uri is 適切に supported.
削除する