-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
perf: various changes #118
Conversation
mattklein123
commented
Oct 5, 2016
- Don't use fmt::format() in HTTP/1.1 codec hot path
- Allow x-request-id generation to be disabled
- Don't do tracing mutation if tracing is not enabled
- Allow router dynamic stats to be disabled
- Don't generate useless random numbers for null runtime
1) Don't use fmt::format() in HTTP/1.1 codec hot path 2) Allow x-request-id generation to be disabled 3) Don't do tracing mutation if tracing is not enabled 3) Allow router dynamic stats to be disabled 4) Don't generate useless random numbers for null runtime
@lyft/network-team |
output_buffer_.add(method); | ||
output_buffer_.add(" "); | ||
output_buffer_.add(path); | ||
output_buffer_.add(" HTTP/1.1\r\n"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
use CRLF as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another function call for no particular reason
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, sound good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
…oxy#118) Signed-off-by: Yuchen Dai <[email protected]>
Previously, TLS inspector didn't support TLSv1.3 and clients configured to use only TLSv1.3 were not recognized as TLS clients. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process. Signed-off-by: Piotr Sikora <[email protected]>
Previously, TLS inspector didn't support TLSv1.3 and clients configured to use only TLSv1.3 were not recognized as TLS clients. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process. Signed-off-by: Piotr Sikora <[email protected]>
Previously, TLS inspector didn't support TLSv1.3 and clients configured to use only TLSv1.3 were not recognized as TLS clients. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process. Signed-off-by: Piotr Sikora <[email protected]>
Previously, TLS inspector didn't support TLSv1.3 and clients configured to use only TLSv1.3 were not recognized as TLS clients. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process. Signed-off-by: Piotr Sikora <[email protected]>
zh-translation: docs/root/intro/arch_overview/advanced/advanced.rst
Co-authored-by: Anuraag Agrawal <[email protected]>