Closed Bug 1678312 Opened 4 years ago Closed 2 months ago

TLS handshake timings are not correct

Categories

(Core :: Networking: HTTP, defect, P2)

defect
Points:
3

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox132 --- fixed

People

(Reporter: dragana, Assigned: kershaw)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged][necko-priority-queue])

Attachments

(2 files)

Handling of socket notification in nsHttpTransaction is not correct.

I will not have time to work on this bug, so I am unassigning myself.

Assignee: dd.mozilla → nobody
Status: ASSIGNED → NEW
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-new]
Flags: needinfo?(kershaw)

Do we know in what way the notification is not correct?

(In reply to Randell Jesup [:jesup] (needinfo me) from comment #2)

Do we know in what way the notification is not correct?

Sorry, I haven't looked into this. I'll do this soon.

Btw, when trying to land bug 1801292 that fixed some of the TLS timings.

In our current code, we set the timing secureConnectionStart to the time when the HTTP/3 connection is establised here, which is not right.
To fix this, we might need to expose this information from neqo.

Flags: needinfo?(kershaw)
Whiteboard: [necko-triaged][necko-priority-new] → [necko-triaged][necko-priority-review]
Whiteboard: [necko-triaged][necko-priority-review] → [necko-triaged][necko-priority-next]
Points: --- → 3
Whiteboard: [necko-triaged][necko-priority-next] → [necko-triaged]
Flags: needinfo?(kershaw)

Having those timings be correct might help with performance profiling.

See Also: → 1801292
Assignee: nobody → kershaw
Flags: needinfo?(kershaw)
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-queue]

Before this patch, TelemetryReportChannel(timedChannel, true) was only called within nsLoadGroup::TelemetryReport() when all requests were completed in the load group.
However, SetDefaultLoadRequest(nullptr) could be called before this, resulting in mDefaultLoadRequest being set to null and causing page load metrics to sometimes not be reported.
To fix this, this patch moves TelemetryReportChannel(timedChannel, true) to the point where mDefaultLoadRequest is completed.

Pushed by kjang@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dfc31bf59096 Make sure page load telemetry probes are reported properly, r=necko-reviewers,valentin https://hg.mozilla.org/integration/autoland/rev/aa6305a65fb5 Mapping Http3Event::Tag::AuthenticationNeeded to NS_NET_STATUS_TLS_HANDSHAKE_STARTING, r=necko-reviewers,valentin
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: