Bug 104352 - [Qt] new http/tests/xmlhttprequest/post-blob-content-type-sync.html and ~async.html fail since introduced in r136893
Summary: [Qt] new http/tests/xmlhttprequest/post-blob-content-type-sync.html and ~asyn...
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Alexander Shalamov
Keywords: Qt, QtTriaged
Depends on:
Blocks: 87008 99983
  Show dependency treegraph
Reported: 2012-12-07 01:03 PST by János Badics
Modified: 2014-02-03 03:23 PST (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Alexander Shalamov 2012-12-11 00:01:16 PST
I will take a look at this bug.
Comment 2 Alexander Shalamov 2012-12-11 03:38:50 PST
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?
Comment 3 Jocelyn Turcotte 2014-02-03 03:23:49 PST
=== 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.