0ab6867ae5
Right now the proxying of cloudflared -> unix socket is a bit of a no man's land, where we do not have the ability to specify the actual protocol since the user just configures "unix:/path/" In practice, we proxy using an HTTP client. But it could be that the origin expects HTTP or HTTPS. However, we have no way of knowing. So how are we proxying to it? We are configuring the http.Request in ways that depend on the transport and edge implementation, and it so happens that for h2mux and http2 we are using a http.Request whose Scheme is HTTP, whereas for quic we are generating a http.Request whose scheme is HTTPS. Since it does not make sense to have different behaviours depending on the transport, we are making a (hopefully temporary) change so that proxied requests to Unix sockets are systematically HTTP. In practice we should do https://github.com/cloudflare/cloudflared/issues/502 to make this configurable. |
||
|---|---|---|
| .. | ||
| ingress.go | ||
| ingress_test.go | ||
| origin_connection.go | ||
| origin_connection_test.go | ||
| origin_proxy.go | ||
| origin_proxy_test.go | ||
| origin_request_config.go | ||
| origin_request_config_test.go | ||
| origin_service.go | ||
| origin_udp_proxy.go | ||
| rule.go | ||
| rule_test.go | ||