Two page loading stalls reported: 1] with squid doing https (h1) proxying to an an h1 https origin 2] with spdyprxy doing https (spdy/3.1) proxying to any https origin
(In reply to Patrick McManus [:mcmanus] from comment #0) > > > 2] with spdyprxy doing https (spdy/3.1) proxying to any https origin scratch that - that turns out to only be a failure with an uncommitted development branch. #1 is the only issue here.
status-firefox32: --- → unaffected
status-firefox33: --- → affected
status-firefox34: --- → affected
status-firefox35: --- → affected
Assignee: nobody → mcmanus
Status: NEW → ASSIGNED
reporter verifies the try build resolves the issue.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Comment on attachment 8501330 [details] [diff] [review] Page stalls proxying over https part 1 the feature this fixes is new in 33.. too late for that release, but its a conservative and targeted fix that should be uplifted. Approval Request Comment [Feature/regressing bug #]:378637 [User impact if declined]: potential stalls during page load when using new https proxying feature (in gecko 33) [Describe test coverage new/current, TBPL]: try is good and has merged to m-c. reporter verifies fix [Risks and why]: very conservative change only in code path of new feature [String/UUID change made/needed]: none
Attachment #8501330 - Flags: approval-mozilla-aurora?
Comment on attachment 8501330 [details] [diff] [review] Page stalls proxying over https part 1 Aurora+
Attachment #8501330 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
status-firefox33: affected → wontfix
status-firefox34: affected → fixed
status-firefox35: affected → fixed
You need to log in before you can comment on or make changes to this bug.