Open Bug 1572546 Opened 8 months ago Updated 3 months ago

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

Categories

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

task

Tracking

()

People

(Reporter: ehsan, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

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.

Priority: -- → P2
Whiteboard: [necko-triaged]

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

Flags: needinfo?(dd.mozilla)

(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.

Flags: needinfo?(dd.mozilla)

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.)

Blocks: 1590107
You need to log in before you can comment on or make changes to this bug.