Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support session tickets on client, RFC 5077 #14425
Please answer these questions before submitting your issue.
Should this be an issue in the gRPC issue tracker?
Create new issues for bugs and feature requests. An issue needs to be actionable. General gRPC discussions and usage questions belong to:
Please don't double post your questions in more locations; we are monitoring both channels, and the time spent de-duplicating questions is better spent answering more user questions.
What version of gRPC and what language are you using?
grpc-core 1.8.4, both python grpcio & proprietary rust binding on top of grpc-core
What operating system (Linux, Windows, …) and version?
What runtime / compiler are you using (e.g. python version or version of gcc)
What did you do?
What did you expect to see?
Client should resume previously established tls session using ticket issued by server.
What did you see instead?
Client sends ClientHello to server with empty tls ticket extension, they have to go through full tls handshake again.
After further investigation it looks like grpc-core provides neither tickets support on client/server by default nor any means to configure it.
One of possible suggestions is to add the following interface & re-expose it from python and wire it up with boringssl session ticket support. The expectation is that user creates cache once & passes it to different channels via creation arguments.
Other ideas are welcome.
Anything else we should know about your project / environment?