The default bug view has changed. See this FAQ.

Status

()

Core
Networking: HTTP
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: mcmanus, Assigned: mcmanus)

Tracking

14 Branch
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
603514 had merge conflicts with spdy code. The primary effect of this was I didn't merge a couple prefs that were instead left hardcoded with different default values.
(Assignee)

Updated

5 years ago
Blocks: 742935
(Assignee)

Comment 1

5 years ago
Created attachment 613348 [details] [diff] [review]
patch 0
Assignee: nobody → mcmanus
Status: NEW → ASSIGNED
Attachment #613348 - Flags: review?(honzab.moz)
Comment on attachment 613348 [details] [diff] [review]
patch 0

Review of attachment 613348 [details] [diff] [review]:
-----------------------------------------------------------------

r=honzab

Telemetry is the next step.

::: netwerk/protocol/http/nsHttpHandler.h
@@ +242,5 @@
> +    {
> +        return mCapabilities & NS_HTTP_ALLOW_PIPELINING;
> +    }
> +
> +    bool GetPipelineRescheduleOnTimeout()

Maybe call this GetAllowPipelineRescheduleOnTimeout()  But this way it reflects the pref..  Up to you.
Attachment #613348 - Flags: review?(honzab.moz) → review+
(Assignee)

Comment 3

5 years ago
(In reply to Honza Bambas (:mayhemer) from comment #2)

> 
> Telemetry is the next step.
> 

yes.. probably something that tracks all the different red event types.
(Assignee)

Comment 4

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/e819f766c586
https://hg.mozilla.org/mozilla-central/rev/e819f766c586
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.