Closed Bug 112479 Opened 24 years ago Closed 24 years ago

HTTP needs complete support for nsIUploadChannel

Categories

(Core :: Networking: HTTP, defect, P1)

defect

Tracking

()

RESOLVED FIXED
mozilla0.9.8

People

(Reporter: darin.moz, Assigned: darin.moz)

Details

Attachments

(1 file, 1 obsolete file)

HTTP needs complete support for nsIUploadChannel
Severity: normal → major
Status: NEW → ASSIGNED
Keywords: mozilla1.0
Priority: -- → P2
Target Milestone: --- → mozilla0.9.8
this is P1 critical for editor publish support.
Priority: P2 → P1
Attached patch v1.0 patch (obsolete) — Splinter Review
somewhat complicated logic in SetUploadStream, but this should do the trick.
Keywords: patch
- improved comment in nsHttpTransaction::SetupRequest - added extra brace around first if (contentType < 0) - substituted AppendInt for PR_snprintf
Attachment #64419 - Attachment is obsolete: true
Comment on attachment 64552 [details] [diff] [review] v1.1 patch - revised per comments from dougt looks good.
Attachment #64552 - Flags: review+
Comment on attachment 64552 [details] [diff] [review] v1.1 patch - revised per comments from dougt sr=alecf
Attachment #64552 - Flags: superreview+
fixed-on-trunk
fixed-on-trunk (and i really mean it!)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
this seems to have caused bug 119625
In nsHttpChannel::SetUploadStream, it seems that the line mUploadStream = stream; should be at the beginning at the function, not at the end. The old code was first initialising mUploadStream, and bug #119625 doesn't seem to occur with that line moved. I don't understand this code at all, so I'm sorry if I'm telling stupid things :)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: