-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix upstream default port when HTTP_PROXY #1440
Merged
Merged
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
eguzki
changed the title
Fix upstrem default port when HTTP_PROXY
Fix upstream default port when HTTP_PROXY
Jan 31, 2024
tkan145
requested changes
Feb 1, 2024
It turns out that the camel use case is affected. Fix added. |
tkan145
approved these changes
Feb 5, 2024
LGTM. Please also update the CHANGELOG file |
Added CHANGELOG entry. Since there are new commits in the PR, I need new approval to be fair. |
+1 feel free to merge when you are ready |
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
When the gateway is configured to use
http_proxy
(i.e proxy between APIcast and some plain HTTP/1.1 upstream), and the port is not specified inapi_backend
service attribute, the request going from APIcast has a wrong absolute URI pathNote that the port in the request line is
nil
.The issue is not happening forIt turns out that the camel use case is affected forhttps_proxy
based connections.https_proxy
use case.Verification Steps
Request should return 200
The request path should not contain
nil
port