fix(#1448): Fix proxy configuration confusion #1883
Closed
+11
−4
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.
Description
Fix a confusion between system proxy and explicit bruno proxy configuration
It fixes #1448
Contribution Checklist:
Status
This patched have been tested with http proxy:
It should have no effects on SOCK proxy (And I don't know if the issue exists on those config anyway)
Description of the issue
Given the following configuration
On http request (to http://neverssl.com): it try to send the http request to http://neverssl.com:8080 (wrong port) via the proxy http://explicit.proxy:9000 (correct proxy)
On https request (to https://www.example.com): it try send a CONNECT ::1 request (can be seen with wireshark)
An issue is opened on the proxy-agent repo: TooTallNate/proxy-agents#298 even tho I don't know if it's an axios issue, a proxy-agent issue or a bruno issue
Minimal example
Here the following result: