5
9 Comments

What HTTP client do you use? And what do you think about it?

I'm developing a HTTP client called WebMaestro because I had a need for a client where it was easy to use certificates for client and server authentication. This was something I didn't think was easy to do in Postman, Insomnia or SoapUI.

I would like to know what HTTP clients you are using and what features they have that you love and what problems you have with them?

on October 30, 2019
  1. 2

    I use Insomnia. It's simple and does the job for me :)

    1. 1

      Do you pay for it and use the E2EE sync feature?

      1. 1

        Nope am a solo developer. I don't have a need for it at the moment.

  2. 1

    I just use a vscode plugin

      1. 1

        Its name is just "REST Client"

  3. 1

    For me, I have Postman setup so I can use do one-click tests and automated tests as well.
    But when I am actively developing, I use this command line client HTTPie for tests.
    It's slick. My favourite feature is that it allows me to save and reuse sessions. As simple as http --session=user -f POST https://localhost:port/endpoint, so cookies, headers, auth credentials e.t.c are persisted and can be reused.

    ps: When you say "use certificates for client and server authentication", do you mean using client side certificates for the SSL communication? or some custom/standar server authentication mechanisms requiring certificates?

    1. 2

      Do you pay for Postman and use the team collaboration and API mocking?

      Reusing sessions seems like a sweet feature!

      The current project I'm working on has a Rest API that requires certificates for client authentication against the server. And it requires different certificates for DEV, SIT, QA and PROD environments, so as a developer I developed my own solution when I couldn't (or wouldn't :D) find another solution!

      Also, I had a need to mock some APIs so I included a very basic Http server to achieve this.

      1. 1

        No. I am currently on the Postman plan(For individuals and small teams). I am not using the API mocking feature right now, but it's something I would look into.

        For the team collaboration feature, I have my Collections setup, so I'll definitely be using it later on as I onboard new developers to the project I am currently working on.

        I see regarding authentication. It makes sense then, to build a custom tool that suits your needs. :)