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

Error resolving proxy #1391

Closed
jawira opened this issue Sep 17, 2020 · 4 comments · Fixed by #1393
Closed

Error resolving proxy #1391

jawira opened this issue Sep 17, 2020 · 4 comments · Fixed by #1393
Labels
Milestone

Comments

@jawira
Copy link
Contributor

jawira commented Sep 17, 2020

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?

@siad007
Copy link
Member

siad007 commented Sep 17, 2020 via email

@siad007
Copy link
Member

siad007 commented Sep 18, 2020

@jawira would you mind to check the pr? thx

@jawira
Copy link
Contributor Author

jawira commented Sep 19, 2020

@jawira
Copy link
Contributor Author

jawira commented Sep 19, 2020

@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
Labels
Development

Successfully merging a pull request may close this issue.

2 participants