What's Changed
- The behavior of using the default version of the HTTP protocol is not appropriate, because all HTTP servers support HTTP/1.1, but not all HTTP servers support HTTP/2, so it is not appropriate to select HTTP/2 by default when both versions are supported. So in this PR, we use HTTP/1.1 by default when
"http1"
is enabled - There's no HTTP proxy implementation in Volo-HTTP, and when running unit tests using nodes in mainland China, the test fails due to abnormal access to
httpbin.org
. So we addHttpProxyLayer
in Volo-HTTP, it supports HTTP proxy defined in rfc7230 and it can read address from environment variable (http_proxy
andHTTP_PROXY
) or be set manually. - There are some inappropriate aspects of the previous DNS Resolver implementation, we adjust it in Volo-HTTP and Volo-gRPC which is copied from Volo-HTTP with some modifies.
- For better observability, we add
SpanProvider
for Volo-HTTP, it can enter a user defined span when serving a request.
Pull Request: chore(volo-http): adjust some codes by @yukiiiteru in #590
Full Changelog: volo-http-0.4.0-rc.4...volo-http-0.4.0-rc.5