Open Bug 1373348 Opened 7 years ago Updated 2 years ago

Optimize closing transaction in nsHttpChannel::ReadFromCache when cache wins the race

Categories

(Core :: Networking: Cache, defect, P3)

Product:
Core
Component:
Networking: Cache
Type:
defect

Tracking

()

People

(Reporter: michal, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-backlog]) 

From bug 1367742 comment 26:
> For a followup bug: the proper way for h1 (whether h1/2 should be hidden
> from nshttpchannel) is to let the transaction finish and just discard the
> data.  This is the idea of 'soft closing' a transaction.  To be even more
> perfectionist the transaction should be hard-canceled when the remaining
> amount of data is too large and would just waste bandwidth.  The threshold
> is hard to figure out, so definitely not something to be done for 57 or 58,
> but definitely something to be filed at least.
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.