orborn
HTTPoison proxy option not working
I have this curl request
curl -x "http://proxy-server.com:8001" -k "https://httpbin.org/ip"
The curl request is going through the proxy server and I’m getting at each hit a new ip address (which is the expected behavior).
But when I try with HTTPoison it’s not working as expected.
I tried these codes
HTTPoison.get!("https://www.httpbin.org/ip", [], [proxy: {"http://proxy-server.com"}])
HTTPoison.get!("https://www.httpbin.org/ip", [], [{:proxy, "http://proxy-server.com"}])
What am I doing wrong ?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 2 of 2 Posts
al2o3cr
The
proxyoption expects either a binary or a two-element tuple of{host, port}, so that first one is not going to work.As for the second one, the URL doesn’t have a port specified like the one in the
curlcommand does. Maybe that’s the problem?It would be useful to get more detail on “not working as expected” - what happens (error message, stack trace, etc) when you attempt those
HTTPoisoncalls? I don’t have a proxy server handy to test with, so I can’t see what you’re seeing.orborn
Thank you for your reply and the clear explanation.
I’ll try to tweak the code a bit more based on what you said.