Change description:
Chrome's XSS Auditor should block pages by default, rather than filtering out suspected reflected XSS. Moreover, we should remove the filtering option, as breaking specific pieces of page's script has been an XSS vector itself in the past.
Changes to API surface:
1. We will default to acting as though `X-XSS-Protection: 1; mode=block` was sent.
2. If `X-XSS-Protection: 1` is sent, we will treat it like `X-XSS-Protection: 1; mode=block`.
Links:
Public standards discussion: The XSS auditor is a proprietary pile of heuristics.
Support in other browsers:
IE has an auditor which is a proprietary pile of heuristics.
Safari has an auditor which is a proprietary pile of heuristics.
Firefox has no auditor.
Comment 1 by bugdroid1@chromium.org
, Nov 24 2016