Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crypto/tls: Config.ClientSessionCache has wrong field name in its doc #21519

Closed
artyom opened this issue Aug 18, 2017 · 1 comment
Closed

crypto/tls: Config.ClientSessionCache has wrong field name in its doc #21519

artyom opened this issue Aug 18, 2017 · 1 comment

Comments

@artyom
Copy link
Member

@artyom artyom commented Aug 18, 2017

crypto/tls.Config.ClientSessionCache doc refers to this field as SessionCache instead of ClientSessionCache:

// SessionCache is a cache of ClientSessionState entries for TLS session
// resumption.
ClientSessionCache ClientSessionCache
@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Aug 18, 2017

Change https://golang.org/cl/56832 mentions this issue: crypto/tls: fix docstring of Config.ClientSessionCache

@gopherbot gopherbot closed this in 85deaf6 Aug 25, 2017
@golang golang locked and limited conversation to collaborators Aug 25, 2018
FiloSottile pushed a commit to FiloSottile/go that referenced this issue Oct 12, 2018
Closes golang#21519

Change-Id: I1247e9435de93aae7e4db2b6e8e5be1b010c296b
Reviewed-on: https://go-review.googlesource.com/56832
Reviewed-by: Avelino <t@avelino.xxx>
Reviewed-by: Adam Langley <agl@golang.org>
FiloSottile pushed a commit to FiloSottile/go that referenced this issue Oct 12, 2018
Closes golang#21519

Change-Id: I1247e9435de93aae7e4db2b6e8e5be1b010c296b
Reviewed-on: https://go-review.googlesource.com/56832
Reviewed-by: Avelino <t@avelino.xxx>
Reviewed-by: Adam Langley <agl@golang.org>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.