151–160 of 209 posts
Earlier quoted context omitted.
That's very odd. Will look into this.
And the Cookie header isn't sent? (using it on Firefox 106.1).
Entering "news.ycombinator.com" and pressing send gives me an error.
Nothing to take away from all of this, but please learn cURL. Postman and all its alternatives are great and all, but they also hide a lot of things that will hinder your debugging skills. As an alternative try httpie. Not because CLIs are cool but because you can see the headers and the raw response more easily. Developers need to understand what content type is, what response headers are, how to limit them, how to…
The command line fucking SUCKS for sending anything beyond basic HTTP requests.
If you are a minimalist, and are using VS Code, try https://marketplace.visualstudio.com/items?itemName=humao.re... which is a pure text syntax to describe API requests, and execute them right from the editor window. I now have api.http text file in every API-first project I am building and I love it.
If you are a minimalist, and are using VS Code, try https://marketplace.visualstudio.com/items?itemName=humao.re... which is a pure text syntax to describe API requests, and execute them right from the editor window. I now have api.http text file in every API-first project I am building and I love it.
Do you have a single api.http file or do you you multiple {route}.http files?
Personally what I do is I script out full API workflows in different files. So one file might login, then POST to add an object, then GET that object off an endpoint, then patch that endpoint, then trigger the GET object again.
Another workflow might login, upload an image, get that image, etc. For me the scripting is what makes this appealing.
But you could setup one file that documents and tests all your endpoints similar to Postman.
If you are a minimalist, and are using VS Code, try https://marketplace.visualstudio.com/items?itemName=humao.re... which is a pure text syntax to describe API requests, and execute them right from the editor window. I now have api.http text file in every API-first project I am building and I love it.
I like this one because it's easy to keep API workflows with my projects. The scripting ability here is phenomenal. However only really useful if you code in VS Code.
In the end, I think hurl [0] is nicer, because it’s open source and it’s a cli tool (and VS code also has a syntax highlighting plugin for it), making it editor independent.
I have been trying out https://hurl.dev and so far been really liking it. Plain text format, everything runs very quickly locally, it can capture data from previous requests to run workflows and serve as a testing tool.
Give it a try: https://stepci.com
It's free and open-source on GitHub, built by the community!
Disclaimer: I'm the original author