plain-http-upstream is configured with external 3scale backend #1495
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tkan145
approved these changes
Sep 19, 2024
eguzki
force-pushed
the
dev-environment-with-backend
branch
from
1498372 to
af4a681
Compare
tkan145
approved these changes
Sep 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
plain-http-upstream is configured with external 3scale backend. Useful to inspect traffic (and connection setup/teardown) between apicast and backend.
Changed from
kennethreitz/httpbinecho api toquay.io/kuadrant/authorino-examples:talker-apibecause the former one was closing connections after each request. Maybe it was a HTTP/1.0 server?? IDK. I did not dig into it. But the new echo-api keeps the connection open (by default) waiting for more requests (until idle timeout expires).