Bug 89278 - [GTK] New http/tests/cache/xhr-vary-header.html fails
Summary: [GTK] New http/tests/cache/xhr-vary-header.html fails
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Keywords: Qt, QtTriaged
Depends on:
Blocks: 87008 88925
  Show dependency treegraph
Reported: 2012-06-16 01:40 PDT by Csaba Osztrogonác
Modified: 2017-03-11 11:00 PST (History)
6 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Osztrogonác 2012-06-16 01:40:27 PDT
New test introduced in http://trac.webkit.org/changeset/120339 fails on Qt WK2:

--- /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/cache/xhr-vary-header-expected.txt
+++ /home/webkitbuildbot/slaves/release64bitWebKit2_EC2/buildslave/qt-linux-64-release-webkit2/build/layout-test-results/http/tests/cache/xhr-vary-header-actual.txt
@@ -3,7 +3,7 @@
 Make cross origin request 
 PASS responseText is 'Cross origin response'
-PASS responseText is 'Same origin response'
+FAIL responseText should be Same origin response. Was Cross origin response.
 PASS responseText is 'Cross origin response'
 PASS successfullyParsed is true

Maybe we need some change in Source/WebCore/platform/network/qt/ResourceHandleQt.cpp .
(But I'm not sure, because it passes on Qt-WK1, but fails only on Qt-WK2)
Comment 1 Csaba Osztrogonác 2012-06-16 01:42:36 PDT
I skipped it to paint the bot green - r120525. Please unskip it with the proper fix.
Comment 2 Alexey Proskuryakov 2012-06-16 12:44:02 PDT
It's surprising that WK1 and WK2 behaves differently. Perhaps Qt DumpRenderTree has network cache disabled completely somehow?

Anyway, the proper fix would be in networking code outside WebKit. You could consider applying the same workaround I made for Mac in the meanwhile.
Comment 3 Sergio Villar Senin 2012-09-14 08:43:11 PDT
Exactly the same outcome in the WK2 GTK+ port