-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
ProxyHelper handles proxy URLs with trailing slash. #1597
Conversation
Added two missing test cases. 1. Trailing slash in proxy URL. 2. No user:password provided in proxy URL.
Can one of the admins verify this patch? |
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed, please reply here (e.g.
|
Notifying @kchodorow, who seems to have worked on the ProxyHelper before. |
Jenkins, test this please. |
LGTM, the build failure is unrelated. Please sign the CLA and I'll merge this in. |
CLA: 'I signed it!' |
CLAs look good, thanks! |
Having a proxy URL defined with a trailing slash caused an exception. `Proxy address ... is not a valid URL"` This pull request fixes this issue. I also added two test cases for this issue. 1. Trailing slash in proxy URL. 2. No user:password provided in proxy URL. Closes #1597. -- Reviewed-on: bazelbuild/bazel#1597 MOS_MIGRATED_REVID=129721433
Having a proxy URL defined with a trailing slash caused an exception.
Proxy address ... is not a valid URL"
This pull request fixes this issue.I also added two test cases for this issue. 1. Trailing slash in proxy URL. 2. No
user:password provided in proxy URL.