[erlang-questions] HTTP clients

[Tim Watson]

httpc is perfectly fine for most applications - Max had a slightly
more demanding use case than is usual for a generic http client and
clearly it made sense for him to do something specific in that area.

I've used ibrowse in situations where I'm stuck behind a corporate
proxy and inets won't upgrade the socket to ssl, making it impossible
to access https urls. This was mentioned on the list and I'm pretty
sure it's on the 'TODO' list for the otp team to fix. Apart from that,
httpc has never let me down and the scenarios where I'm using ibrowse
are very lightweight, so I can't comment on its utility very broadly.

On 18 February 2012 20:33, Zabrane Mickael <zabrane3@REDACTED> wrote:
>
> On Feb 18, 2012, at 9:26 PM, Garrett Smith wrote:
>
> On Sat, Feb 18, 2012 at 9:30 AM, Tristan Sloughter
> <tristan.sloughter@REDACTED> wrote:
>
> Now to http clients instead of servers :)
>
>
> Over the years I've bounced between httpc, lhttpc and ibrowse (I think
>
> that's all...) and was wondering what opinions people had on the 3 and which
>
> are still developed and used in production.
>
>
> It seems ibrowse has the most features and most development going on.
>
>
> Though examples are lacking for all of them... So on a side note if anyone
>
> has an example of posting form data with ibrowse that would be much
>
> appreciated.
>
>
> If I just need to grab a file, I'll call out to curl :)
>
>
> May be semonce car start from here to make this linked-in driver stable:
> http://www.chrisumbel.com/article/c_from_erlang_curl
>
> Regards,
> Zabrane
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>