crypto/tls: session resumption (session id caching) #18607

Open
tam7t opened this Issue Jan 11, 2017 · 1 comment

Projects

None yet

4 participants

@tam7t
tam7t commented Jan 11, 2017 edited

What version of Go are you using (go version)?

go version go1.7.4 darwin/amd64

What operating system and processor architecture are you using (go env)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"

What did you do?

I have 2 web servers, one that supports TLS session resumption based on a session cache and another that supports session cache and session tickets.

https://play.golang.org/p/9n4OZRjqHh

What did you expect to see?

I had expected the 2nd connection to each server to resume the session.

What did you see instead?

DidResume is only true for the server that supports session ticket resumption.

It appears that session ID caching is not supported in client or server mode. Perhaps the documentation for ClientSessionCache could be a bit more explicit that it is only a cache for session tickets.

@bradfitz bradfitz added this to the Go1.9 milestone Jan 11, 2017
@agl agl was assigned by bradfitz Jan 11, 2017
@FiloSottile
Contributor

Session ID caching is not supported in neither client nor server.

I guess the client side can be documented in Config.ClientSessionCache. Not sure where the docs for the server side could go.

I had to look at the code myself a week ago to confirm this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment