Add TCP support to the proxy #131
Comments
Closed
3 tasks
seanmonstar
added a commit
that referenced
this issue
Jan 24, 2018
The proxy will now try to detect what protocol new connections are
using, and route them accordingly. Specifically:
- HTTP/2 stays the same.
- HTTP/1 is now accepted, and will try to send an HTTP/1 request
to the target.
- If neither HTTP/1 nor 2, assume a TCP stream and simply forward
between the source and destination.
* tower-h2: fix Server Clone bounds
* proxy: implement Async{Read,Write} extra methods for Connection
Closes #130
Closes #131
khappucino
pushed a commit
to Nordstrom/linkerd2
that referenced
this issue
Mar 5, 2019
The proxy will now try to detect what protocol new connections are
using, and route them accordingly. Specifically:
- HTTP/2 stays the same.
- HTTP/1 is now accepted, and will try to send an HTTP/1 request
to the target.
- If neither HTTP/1 nor 2, assume a TCP stream and simply forward
between the source and destination.
* tower-h2: fix Server Clone bounds
* proxy: implement Async{Read,Write} extra methods for Connection
Closes linkerd#130
Closes linkerd#131
khappucino
pushed a commit
to Nordstrom/linkerd2
that referenced
this issue
Mar 5, 2019
There is no telemetry from the controller client currently. This change adds a new scope (`control_`) of metrics including HTTP metrics for the client to the proxy-api.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a new connection is made to the proxy, the proxy will try to determine if it is using HTTP (1 or 2), and if not, consider it a raw TCP connection to just pass through.
For the initial feature, the
SO_ORIGINAL_DSTwill be used to determine where to open a socket to.The text was updated successfully, but these errors were encountered: