Drains tokeninfo response body to enable TCP connection reuse #1511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AuthClient used by
oauthTokeninfo*
filters does not consume response body when token is invalid:skipper/filters/auth/authclient.go
Lines 110 to 114 in e3372b5
According to https://golang.org/pkg/net/http/#Client.Do
That is requests with invalid token prevent tokeninfo TCP connection reuse which leads to higher latencies.
Consider the following setup:
and
Benchmark results:
Consuming response body with:
reduces latencies severalfold:
See also: