-
-
Notifications
You must be signed in to change notification settings - Fork 319
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
Error resolving proxy #1391
Comments
Thanks for the report - this sounds like a refactoring bug as you mentioned
and should be fixed ASAP
Jawira Portugal <notifications@github.com> schrieb am Do. 17. Sept. 2020 um
11:24:
…
Hi, I had the habit to add proxy configuration to my buildfiles. Because
in linux you can set your proxy using an environment variable I simply
passed this variable to a property:
<property name="phing.http.proxy" value="${env.http_proxy}"/>
Currently I don't work behind a proxy anymore, so ${env.http_proxy}
doesn't exists. This wasn't a problem until I updated to *Phing
3.0.0-alpha4*:
$ phing -v
Phing 3.0.0-alpha4
$ phing emoji-list:download
Buildfile: /home/jawira/PhpstormProjects/emoji-catalog/build.xml
Emoji catalog > emoji-list:download:
BUILD FAILED
/home/jawira/PhpstormProjects/emoji-catalog/build.xml:68:98 cURL error 5: Could not resolve proxy: ${env.http_proxy} (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Total time: 0.0630 seconds
Apparently now phing.http.proxy must be a valid proxy if it's declared. I
understand that this could be related to the use of Guzzle library, but do
you thing is it possible to revert to the previous behavior?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1391>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQMYRNVH2N7AIJEZNHORVDSGHIT5ANCNFSM4RQEJAYQ>
.
|
@jawira would you mind to check the pr? thx |
Looks good to me 👍🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I had the habit to add proxy configuration to my buildfiles. Because in linux you can set your proxy using an environment variable I simply passed this variable to a property:
Currently I don't work behind a proxy anymore, so
${env.http_proxy}
doesn't exists. This wasn't a problem until I updated to Phing 3.0.0-alpha4:Apparently now
phing.http.proxy
must be a valid proxy if it's declared. I understand that this could be related to the use of Guzzle library, but do you thing is it possible to revert to the previous behavior?The text was updated successfully, but these errors were encountered: