Bug 104352 – [Qt] new http/tests/xmlhttprequest/post-blob-content-type-sync.html and ~async.html fail since introduced in r136893

• Status: RESOLVED
• Resolution: INVALID
• Component: Tools / Tests

[János Badics]

These two tests fail on Qt since they have been introduced in r136893 with the following diffs:
http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r136894%20(45757)/http/tests/xmlhttprequest/post-blob-content-type-async-diff.txt
http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release/r136894%20(45757)/http/tests/xmlhttprequest/post-blob-content-type-sync-diff.txt

The original bug can be found at:
​https://bugs.webkit.org/show_bug.cgi?id=99983

I will skip these tests on Qt until the problem is solved.

[Alexander Shalamov]

I will take a look at this bug.

[Alexander Shalamov]

Qt networking code adds "application/x-www-form-urlencoded" to request header (qhttpnetworkrequest.cpp:156), if header is empty.

According to http://tools.ietf.org/html/rfc2616#section-7.2.1 , it may be empty and receiver could inspect content or extension of the uri to identify content type. In case when media type remains unknown, recipient should treat body as application/octet-stream.

XHR spec states that when the blob is sent, mime type of the request is the type of the blob and if mime type of the blob is invalid it could be ignored. Just tested with latest chrome and mozilla, they send empty string for content-type header field.

Should I add platform specific test for Qt?

[Jocelyn Turcotte]

=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.