# HTTPoison vs HTTPotion **URL:** \ **Category:** Discussions\ **Created:** [November 2, 2016, 9:26am UTC](https://forum.elixirforum.com/t/httpoison-vs-httpotion/2221 "2016-11-02T09:26:41Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![OvermindDL1](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/overminddl1/32/2677_2.png) [@OvermindDL1](https://forum.elixirforum.com/u/OvermindDL1)\ **Post date:** [November 2, 2016, 2:31pm UTC](https://forum.elixirforum.com/t/httpoison-vs-httpotion/2221/8 "2016-11-02T14:31:42Z")
> [@voltone](#): > > HTTPoison (actually, Hackney) comes with secure HTTPS defaults. Last time I checked other HTTP clients, including HTTPotion/iBrowse, will happily let you pass in an HTTPS URL and connect to the server without any verification of the server’s certificate chain or identity (hostname). Basically they obscure the communication to avoid eavesdropping, but they don’t protect against MitM attacks unless you explicitly pass in all the right TLS configuration options. I can attest to this. We have a Ubiquity thing here that mandates HTTPS for its api connection, but it uses a self-signed cert, thus I had to disable HTTPoisons/Hackneys checking. ^.^ --- _[View the full topic](https://forum.elixirforum.com/t/httpoison-vs-httpotion/2221)._