Closed Bug 73234 Opened 24 years ago Closed 23 years ago

nsInputStreamChannel needs to forward itself as the request in progress events

Categories

(Core :: Networking, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla0.9.1

People

(Reporter: darin.moz, Assigned: rpotts)

Details

Attachments

(2 files)

nsInputStreamChannel needs to forward itself as the request in progress events
(eg. nsHTTPChannel implements nsIProgressEventSink on behalf of the socket
transport).
Blocks: 64833
Keywords: mozilla0.9
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9
Keywords: nsbeta1
dougt, rpotts: can you review this patch?  thx!
Keywords: patch
it looks fine. sr=dougt.
looks good... r=rpotts

-- rick
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Guess what...  the patch was wrong :-(

i'm reopening this one, so I cna make sure that it gets fixed...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
-> rpotts...  I want to make sure that this gets in for 0.9.1
why is it wrong? / what did it break?
I've just attached a new patch to the old patch which correctly passes the
nsInputStreamChannel out as the request - rather than the underlying transport
request...

When the transport request was passed out, the progress info would be ignored by
the DocLoader because it did not recognize the request - ie. an OnStartRequest()
for the request had not been fired (only the OnProgress...)

r/sr=darin
I'll check this in asw soon as I get an a= and the tree opens :-)
r=valeski
blah...
Assignee: darin → rpotts
Status: REOPENED → NEW
Keywords: mozilla0.9mozilla0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
a= asa@mozilla.org for checkin to 0.9.1 (on behalf of drivers).
fix checked in...
Status: NEW → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → FIXED
No longer blocks: 64833
QA Contact: tever → benc
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: