matthias_toepp
I’m trying to get html from an old machine.
I’m able to successfully get a response on the command line with this (and I have a go program working as well):
curl 200.200.200.200/aaa/001 --user "user:password"
I get the error: “HTTP request failed: bad_request” when trying to do that with an Elixir script:
HTTPoison.start()
username = "user"
password = "password"
credentials_encoded = Base.encode64("#{username}:#{password}")
headers = [{"Authorization", "Basic #{credentials_encoded}"}]
case HTTPoison.get("200.200.200.200/aaa/001", headers) do
{:ok, %HTTPoison.Response{status_code: 200, body: body}} ->
IO.puts(body)
{:ok, %HTTPoison.Response{status_code: status_code}} ->
IO.puts("Received response with status code #{status_code}")
{:error, %HTTPoison.Error{reason: reason}} ->
IO.puts("HTTP request failed: #{reason}")
end
I’m able to make simple requests to other servers by altering the code slightly. I know the ip and authentication matches the working curl request, and go program.
Any advice is appreciated.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
smathy
No accept header?
al2o3cr
That error comes from the Hackney machinery responsible for parsing the response; the fact that it’s going down the
{:error, HTTPoison.Error}path means it’s failing to parse the opening line of the response - things like missing headers etc would generally result in anHTTPoison.Responsewith astatus_codeof 400.The code in Hackney suggests some possiblities:
https://github.com/benoitc/hackney/blob/d6d075f9edcbb7e0b5c9418dba5dd34f2c95bc21/src/hackney_http.erl#L194-L227
HTTP/1.1 200 OKbinary:spliton line 196 to not find two partsHTTPwrong? Hard to tell)The most reliable way to troubleshoot this is to capture the EXACT bytes the server is replying with, for instance with
curl --trace:matthias_toepp
Here is the output of curl —trace (showing only the part after the send header):
al2o3cr
curlappears to tolerate just sending\n, but Hackney will not. The spec requires\r\n.matthias_toepp
(deleted)
matthias_toepp
It’s kind of marvelous to me that you were able to figure that out. Thanks for the insight. I guess I’ll try a different http library then.
Maybe I’ll post this as an issue for Hackney. It kind of makes sense as apparently it’s following the spec which you linked to, but on the other hand, from my perspective, curl and go ‘worked’, in terms of getting the job done and httpoison didn’t.
matthias_toepp
I opened an issue relating to this on hackney’s github page:
https://github.com/benoitc/hackney/issues/723
matthias_toepp
Just for the record…I’m told by the maintainers that this issue is now resolved!