Closed Bug 391975 Opened 17 years ago Closed 9 years ago

nsHttpChannel::Suspend/Resume do the wrong thing with partially cached content

Categories

(Core :: Networking: HTTP, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Biesinger, Unassigned)

References

Details

(Whiteboard: [necko-backlog])

if (mTransactionPump) return mTransactionPump->Suspend(); if (mCachePump) return mCachePump->Suspend(); When resuming a partial cache entry, we're reading from the cache pump, and we also have a (suspended) transaction pump. So during the time frame when we're reading from the cache, we need to suspend the cache pump rather than the transaction pump.
How does this affect bug 789932 exactly? Is this something we should worry about?
Blocks: 789932
honza, is this fixed?
Flags: needinfo?(honzab.moz)
Whiteboard: [necko-backlog]
The report is misguided. Suspend/Resume on nsInputStreamPump supports counters. Hence calling Suspend more than once is correct and a pump is resumed only after the equal number of calls to Resume. So, suspending both while reading partial entry is absolutely correct unless I'm missing something.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(honzab.moz)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.