-
Notifications
You must be signed in to change notification settings - Fork 48
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
Provision support for PROXY
url.
#51
Comments
PROXY
url.
I'm not actively working on this, but would be happy to review code to include a feature like this. I'm curious if there are any conventions that other API libraries follow for conventions. I have not seen any myself, but I haven't really used a proxy before. If there is a good way to do it within Faraday, |
Thanks for the reply. There is one more gem that pagerduty recommends from their end for other tasks. I have seen that gem implementing this functionality in the here. I am not sure how efficiently it is working but pretty sure that it handles the proxy error that I am facing. |
We are using the faraday gem, so I was googling "faraday proxy", and came across these docs
Given that, it seems that setting And failing that, it should be straightforward to make it configurable from the constructor and/or a proxy environment variable. |
Hi, Thanks. |
I am currently trying to use the gem to connect to the Pagerduty API from a server which only allows proxy url to access the internet. I would like to request a feature where you can make provisions to allow
proxy
parameter when we createPagerduty::Connection.new
, and when it actually connects usingFaraday
here . Below is the screenshot of the error that I am getting.When I create my own connection using
Faraday
with theproxy
key, it works fine, connects to Pagerduty API and does all the operations. But I would like to use the gem for other features but with this support inbuilt.The text was updated successfully, but these errors were encountered: