Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
FYI Google Chrome 17 issues
#2
Ok well I cannot for the life of me find where the admin pages send httpd headers at.
So unless I find that, and how to patch it in, ill have to come up with an apache rule to send the header.

You can also start up chrome with this switch, but its disables it for everything.

Code:
--disable-xss-auditor
So your shortcut target would look something like this.
Code:
"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-xss-auditor

I also confirmed that this is new with 3.1, if you remove the querystrings from the javascript urls, its avoids this bug. So that has something to do with these false positives.
NEW: SA Admin Toolbar Plugin | View All My Plugins
- Shawn A aka Tablatronix
Reply


Messages In This Thread
FYI Google Chrome 17 issues - by shawn_a - 2012-02-22, 04:37:27
FYI Google Chrome 17 issues - by shawn_a - 2012-02-23, 02:16:20
FYI Google Chrome 17 issues - by shawn_a - 2012-02-23, 03:43:12
FYI Google Chrome 17 issues - by ccagle8 - 2012-02-23, 03:50:46
FYI Google Chrome 17 issues - by shawn_a - 2012-02-23, 03:55:02



Users browsing this thread: 1 Guest(s)