1572546 - Partition the TLS session cache per the origin of the top-level window

Status: RESOLVED FIXED

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

Description

[(no longer active)]

We need to do this for parity with what Chrome is implementing with their HTTP Cache paritioning (see the second message in https://groups.google.com/a/chromium.org/forum/m/#!msg/blink-dev/6KKXv1PqPZ0/3_1nYzrBBAAJ).

We might need to file a separate NSS bug for adding support for this at the NSS level. Not really sure about all of the details here.

Comment 1

[Anne (:annevk)]

Dragana, will this include TLS authentication or should that have its own bug?

Comment 2

[Dragana Damjanovic [:dragana]]

(In reply to Anne (:annevk) from comment #1)

Dragana, will this include TLS authentication or should that have its own bug?

I am not exactly sure what do you mean with TLS authentication. Do you mean certificate verification? I think the answer is that we do not need anything else.

Comment 3

[Anne (:annevk)]

TLS client certificates. (Although thinking about it more that does not make sense as they are more like cookies, so maybe ignore that comment and this one.)

Comment 4

[Anne (:annevk)]

I assume this got fixed elsewhere? Or should this be considered a blocker for bug 1673921?

Comment 5

[Tim Huang[:timhuang]]

The NSS Socket peer Id has been isolated by the OAs, see here. So, I think we have fixed this issue in Bug 1642667.

Dragana, could you confirm this?

Comment 6

[Dragana Damjanovic [:dragana]]

That fixes this issue.