Encoding multipart/form-data HTTP body

HTTPoison wraps hackney so you can avoid translating and supports multipart. Haven’t used it for this myself.

https://github.com/edgurgel/httpoison#multipart

Thanks. A bit of a background I should have posted: I want to avoid using HTTPoison / hackney and use either mint directly or with a wrapper called mojito. Unfortunately these don’t have part that assembles “multipart/form-data” requests, so I either have to find one from some other library, or write one myself.

Ah, I see. Yeah, since they’re pretty new and Mint itself is not necessarily designed for “regular” use cases (although mojito is), you’re likely to have to write something yourself if mojito doesn’t support it.

Out of curiosity, why does it have to be mint?

Hackney has got issues that I stumbled upon recently (among others before), but I don’t think I like how it depends on application configuration either, things get quite difficult once you have to deal with SSL / self-signed certificates or client SSL authentication. And I had fair amount of issues on production with using it too, although not recent. There’s a thread on this forum from 2017 where I argued we need a better built-in HTTP client library in Elixir itself.

Mint comes as close as it gets to what I wanted the standard HTTP client to be, it’s idiomatic Elixir, it’s low level enough that you can build idiomatic clients on top of it (like mojito) and from what I saw really like it’s design. It’s a good reading if one wants to learn how to deal with TCP/SSL connections in Elixir too. Very educational

I think I prefer to put in some effort working on getting it up to desired shape myself rather than plan for another battle agains HTTPoison/hackney.

Got it, that makes sense I’ve had some obscure problems with HTTPoison (hackney) too, although nothing I couldn’t just ignore…

tesla can do MultiPart on all of its backends as far as I know… You are free too choose between hackeny, httpc and ibrowse IIRC…

@NobbZ ah, great catch! It’s there indeed: tesla/lib/tesla/multipart.ex at master · elixir-tesla/tesla · GitHub

I’ll have to think on how to extract this possibly to shared lib but for now I can just include tesla as a proof of concept.

Ah, so you do not actually want to send the request, you just want to have the encoded body?

Then I missunderstood your intial question, but I’m happy that I still was able to help

You did but that’s helpful anyway, I was counting on such example code but didn’t think about Tesla.

does Finch support multipart data request?