Closed danagerous closed 2 weeks ago
Under the covers, we use curl for the actual network connection so if you set the http_proxy or https_proxy environment variables then it should just work.
I don't have a set up like that to test against so I can't be absolutely sure, but it seems like it would work. Let me know.
@mikebowler I think what we(@danagerous and I) need is a way to pass Basic Auth in the header
###
GET https://****/int/jira/browse/PMO-10405
Authorization: Basic username pwd
is this possible?
I've put a change into version 2.4pre2 to follow redirects. Please try this and see what result you get. You can install prerelease versions with:
gem install jirametrics --pre
Did this fix the problem you were having?
Hi Mike. No. I was coming back to say this can be closed. I couldn't get it to work.
Unfortunately our Atlassian product URLs are behind a proxy and I am redirected for authentication causing the connection to fail and throw an error.
I tried encoding my login credentials instead of the token with no luck.
Error message included below. I get the same error with token and with encoded credentials.
I'm curious if there is a way to have these metrics work with a proxy?