set-dangerous-headers.html shouldn't set allowed header to same value
authorjparent@chromium.org <jparent@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Fri, 28 Aug 2009 21:16:54 +0000 (21:16 +0000)
committerjparent@chromium.org <jparent@chromium.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Fri, 28 Aug 2009 21:16:54 +0000 (21:16 +0000)
commit7ecf02f60bf1d149569da9d21a5a524914a65ae5
tree40dfbc70f627fcca73fee11b7b34ca397714104b
parent3c13ecf51ad4da3be65cc5238612330e06a4abe2
set-dangerous-headers.html shouldn't set allowed header to same value
as forbidden headers.  AUTHORIZATION is an allowed header, and the
value is being set to "foobar" like the forbidden headers, which causes
the test to fail when run using http server that doesn't strip the
AUTHORIZATION header.
https://bugs.webkit.org/show_bug.cgi?id=28818

Patch by Julie Parent <jparent@chromium.org> on 2009-08-28
Reviewed by Alexey Proskuryakov.

* http/tests/xmlhttprequest/set-dangerous-headers.html:

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@47873 268f45cc-cd09-0410-ab3c-d52691b4dbfc
LayoutTests/ChangeLog
LayoutTests/http/tests/xmlhttprequest/set-dangerous-headers.html