The problem here is that we only call [SSL_SetResumptionTokenCallback](https://searchfox.org/mozilla-central/rev/4d2a9d5dc8f0e65807ee66e2b04c64596c643b7a/netwerk/base/nsSocketTransport2.cpp#1634) when creating a new `nsSocketTransport`, but the same socket transport would be reused when connecting to https proxy. I think we should call `SSL_SetResumptionTokenCallback` when a new `nsNSSSocketInfo` is created.
Bug 1627654 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The problem here is that we only call [SSL_SetResumptionTokenCallback](https://searchfox.org/mozilla-central/rev/4d2a9d5dc8f0e65807ee66e2b04c64596c643b7a/netwerk/base/nsSocketTransport2.cpp#1634) when creating a new `nsSocketTransport`, but the same socket transport would be reused when connecting to https proxy. In this case, we only save the resumption token for the connection of secure proxy and the token for `www.google.com` is not saved. As a result, the session resumption is failed because the token is missing. I think we should call `SSL_SetResumptionTokenCallback` when a new `nsNSSSocketInfo` is created.