Bug 99690

Summary: [XMLHttpRequest] When String, Document or Blob is sent, Content-Type and encoding is set incorrectly
Product: WebKit Reporter: Alexander Shalamov <alexander.shalamov>
Component: WebCore Misc.Assignee: Alexander Shalamov <alexander.shalamov>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, gyuyoung.kim, rakuco, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch 1
buildbot: commit-queue-
Patch 2 ap: review-

Alexander Shalamov
Reported 2012-10-18 00:27:26 PDT
According to http://www.w3.org/TR/XMLHttpRequest/#the-send-method, content type and encoding should be: String: text/plain and encoding UTF-8 Document: For html document text/html and document encoding (UTF-8 if document encoding is not set). Other documents, application/xml and document encoding (UTF-8 if document encoding is not set). Blob: MIME type of the blob should be used if type is not empty.
Attachments
Patch 1 (86.14 KB, patch)
2012-10-18 00:50 PDT, Alexander Shalamov 		buildbot: commit-queue-
DetailsFormatted DiffDiff
Patch 2 (86.22 KB, patch)
2012-10-18 01:10 PDT, Alexander Shalamov 		ap: review-
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Alexander Shalamov
Comment 1 2012-10-18 00:50:21 PDT
Created attachment 169362 [details] Patch 1 patch for initial review
Build Bot
Comment 2 2012-10-18 01:03:49 PDT
Comment on attachment 169362 [details] Patch 1 Attachment 169362 [details] did not pass mac-ews (mac): Output: http://queues.webkit.org/results/14384895
Alexander Shalamov
Comment 3 2012-10-18 01:10:37 PDT
Created attachment 169366 [details] Patch 2 Fix mac-ews. #if ENABLE(DASHBOARD_SUPPORT) was not handled properly.
Alexey Proskuryakov
Comment 4 2012-10-18 22:59:28 PDT
How did you decide which result is correct, and which is not? This is really a duplicate of bug 11049, and discussion should continue there.
Alexey Proskuryakov
Comment 5 2012-10-18 23:00:28 PDT
*** This bug has been marked as a duplicate of bug 11049 ***
Alexey Proskuryakov
Comment 6 2012-10-18 23:01:14 PDT
Comment on attachment 169366 [details] Patch 2 Formally marking r- due to lack of rationale, but primarily to more discussion to original.
Alexey Proskuryakov
Comment 7 2012-10-18 23:01:27 PDT
move*
Alexander Shalamov
Comment 8 2012-10-19 00:47:46 PDT
(In reply to comment #7) > move* Sorry, I missed original bug when I searched for similar issues. Do you want me to continue working on bug 11049 and reassign it to myself or I should stop working on this issue?
Alexey Proskuryakov
Comment 9 2012-10-19 08:38:55 PDT
> Do you want me to continue working on bug 11049 and reassign it to myself Yes, please! I haven't researched this any time recently, it's possible that WebKit is an outlier now, and needs to be fixed. But if the majority of browsers (by installed base, not by brand) still disagree with the spec, then it's a spec bug. Also, I'd suggest doing this in small steps if possible - that way it wold be easier to find the cause if a site breaks (we would just pin that down to a specific revision).
Note You need to log in before you can comment on or make changes to this bug.