Skip to content
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: parse proxy URI with prepending URL scheme #339

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

ginglis13
Copy link
Contributor

@ginglis13 ginglis13 commented Jan 7, 2025

Issue number:

Closes #338

Description of changes:

parse the URI of the proxy generated from Proxy::new(intercept, proxy_uri) rather than proxy_uri directly, since proxy_uri may be missing a URL scheme and in that case can't be parsed as a URL

Testing done:

An aws-k8s-1.31 node with user data

  [settings.network]
    https-proxy = "<myproxy>:8888"

successfully joins the cluster. is the private ipV4 DNS name of an EC2 instance running tinyproxy in the same VPC as the node.

An aws-k8s-1.31 node with user data

  [settings.network]
    https-proxy = "<fake user>:<fake password>@<myproxy>:8888"

and tinyproxy configured to accept BasicAuth <fake user> <fake password> successfully forwards requests and joins the cluster

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

parse the URI of the proxy generated from Proxy::new(intercept,
proxy_uri) rather than proxy_uri directly, since proxy_uri may be
missing a URL scheme and in that case can't be parsed as a URL

Signed-off-by: Gavin Inglis <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pluto panics when specifying an https-proxy without a URL scheme
1 participant