Closed Bug 650279 Opened 14 years ago Closed 4 years ago

Add timing interface for SSL handshake

Categories

(Core :: Networking, enhancement, P5)

enhancement

Tracking

()

RESOLVED INVALID

People

(Reporter: Honza, Unassigned)

References

Details

(Whiteboard: [firebug-p3][necko-would-take])

Firebug's Net panel is using nsIHttpActivityObserver and nsIActivityDistributor to measure various request phases. But it isn't possible to measure SSL Handshake (also OCSP validation step could be nice to measure). Would it be feasible to append such APIs? Honza
Whiteboard: [firebug-p3]
OCSP is going to get optimized and might probably get also disconnected from a channel/page. However, I am working on the Necko telemetry for (hopefully) the next aurora merge that should also measure SSL timings and anything (or at least most significant) that SSL invokes. We don't have API for measuring that so we are probably going to create some. CC'ing Brian that works on OCSP optimizations.
It should be pretty straightforward to add measurements for certificate path validation in total, and other aspects of the handshake. The detailed information about how long each OCSP request takes may require changes to libpkix, so I filed bug 657584 about that. (Though, we may be able to report this detailed information without changing libpkix since Firefox plugs in its own HTTP implementation to libpkix.)
Severity: normal → enhancement
OS: Windows Vista → All
Hardware: x86 → All
Summary: Firebug: measure SSL timings → Add timing interface for SSL handshake
Version: 1.9.1 Branch → Trunk
Note that the web timing spec has an optional 'secureConnectionStart' field that we could provide if we had this info. http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming/Overview.html We're currently not implementing the field in our first implementation (see bug 576006 and bug 570341)
Blocks: 650129
Blocks: 772589
This paper has some data on time taken by OCSP: http://www.internetsociety.org/sites/default/files/12_4.pdf (just see the table 2 on page 4) Note the large variance, and also the variance in median values for different responders. I am not sure of the implications of this on the Telemetry though.
Whiteboard: [firebug-p3] → [firebug-p3][necko-would-take]
Priority: -- → P5

Is this Bug still relevant or can it be closed by now?

Flags: needinfo?(odvarko)

Thank you for the note, closing.
Honza

Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(odvarko)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.