upstream starttls transport socket support chaining arbitrary transport socket instead of RawBuffer
Open
area/connection
enhancement
no stalebot
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 430
Description
upstream starttls transport socket support chaining arbitrary transport socket instead of RawBuffer
I'm filing this just to record that this is a known limitation, I think this configuration is uncommon. @cpakulski
RawBufferSocket hard-codes RawBufferSocket for the initial plaintext part of the session but you might want to chain UpstreamProxyProtocolSocket
This came up on https://github.com/envoyproxy/envoy/pull/27437
Contributor guide
Assessment
This issue has not been assessed yet.