6212 2005-12-22 23:12:19 -0800 Investigate disallowing some XMLHttpRequest headers from being set via setRequestHeader 2007-01-15 10:19:15 -0800 1 1 1 Unclassified WebKit XML 420+ Mac OS X 10.4 RESOLVED FIXED InRadar P2 Normal --- 1 ap webkit-unassigned alice.barraclough bugs-webkit ian oldest_to_newest 26406 0 ap 2005-12-22 23:12:19 -0800 Firefox blocks setting some XMLHttpRequest headers for security reasons. All or most of these are already overridden by the network layer in WebKit, but that needs to be verified, and the checks should probably be added to the cross-platform layer. See: http://whatwg.org/specs/web-apps/current-work/#setrequestheader https://bugzilla.mozilla.org/show_bug.cgi?id=302809 https://bugzilla.mozilla.org/show_bug.cgi?id=302263 https://bugzilla.mozilla.org/show_bug.cgi?id=308484 26690 1 darin 2005-12-26 17:54:22 -0800 I don't necessarily agree that we should add the prohibition to the cross-platform layer. But it is indeed worth researching this. I don't really like having a P1 bug for something that might not even be broken, though. 26699 2 ap 2005-12-26 21:52:58 -0800 (In reply to comment #1) I'm not sure if this counts as broken, but WebKit at least allows overriding Via (https:// bugzilla.mozilla.org/show_bug.cgi?id=302263#c5) and doesn't ignore Content-Length set on empty requests (https://bugzilla.mozilla.org/show_bug.cgi?id=302263#c17). Possibly more. 28076 3 alice.barraclough 2006-01-09 16:26:19 -0800 <rdar://problem/4403688> 28480 4 ap 2006-01-15 02:42:54 -0800 It is also somewhat unclear how security violations should be handled in different cases (silently ignoring vs. throwing). 30436 5 darin 2006-01-28 17:35:27 -0800 Setting this to P2. If we find any real examples of problems, they might qualify as P1 bugs. 34779 6 ap 2007-01-15 10:19:15 -0800 A fix was committed in revision 18863 (brought in sync with the draft spec).