Show HN: I created Postwoman, an online, open-source API request builder
1–10 of 110 posts
Re: Show HN: I created Postwoman, an online, open-source API request builder
#2Don't CORS restrictions basically render this whole tool useless?
Re: Show HN: I created Postwoman, an online, open-source API request builder
#3Don't CORS restrictions basically render this whole tool useless?
It indeed seems to be totally broken.
Re: Show HN: I created Postwoman, an online, open-source API request builder
#4Don't CORS restrictions basically render this whole tool useless?
I don't understand. Plus it has 1700 stars on github.
Re: Show HN: I created Postwoman, an online, open-source API request builder
#5Don't CORS restrictions basically render this whole tool useless?
I suppose it's useful for APIs with permissive CORS headers. Maybe there's also some way to run it locally as a separate app with SOP disabled?
Maybe something like:
$ chromium-browser --disable-web-security --user-data-dir="/tmp" --kiosk https://liyasthomas.github.io/postwoman/
Re: Show HN: I created Postwoman, an online, open-source API request builder
#6Don't CORS restrictions basically render this whole tool useless?
I suppose it's useful for APIs with permissive CORS headers. Maybe there's also some way to run it locally as a separate app with SOP disabled? Maybe something like: $ chromium-browser --disable-web-security --user-data-dir="/tmp" --kiosk https://liyasthomas.github.io/postwoman/ Unrelated, meta note: why does indiehackers need a separate interstitial splash screen, visible for ~4-5 seconds to load a simple article pa…
load balancer /s
Re: Show HN: I created Postwoman, an online, open-source API request builder
#7Don't CORS restrictions basically render this whole tool useless?
~~Does Postman work with JS? I've used it with Python.~~
Oh nvm I'm thinking of a different service
Re: Show HN: I created Postwoman, an online, open-source API request builder
#8Don't CORS restrictions basically render this whole tool useless?
It seems the user created this because they thought that Postman required too many resources as an Electron app.
I'm not sure why they didn't just use a commandline tool (e.g. httpie [1]) that would work with any API, rather than just those with permissive CORS headers.
[1]: https://httpie.org/
Re: Show HN: I created Postwoman, an online, open-source API request builder
#9Don't CORS restrictions basically render this whole tool useless?
it could proxy the requests through a server.
Re: Show HN: I created Postwoman, an online, open-source API request builder
#10Don't CORS restrictions basically render this whole tool useless?
It seems the user created this because they thought that Postman required too many resources as an Electron app. I'm not sure why they didn't just use a commandline tool (e.g. httpie [1]) that would work with any API, rather than just those with permissive CORS headers. [1]: https://httpie.org/
So Postman used to be a lightweight Chrome plugin. Then its developers turned it into an electron app with lots and lots and lots of features. They did this as a vehicle to begin offering paid features and enterprise plans.
To your second point, despite years of writing Curl some times its nice to have an interface and for some people that is their personal preference.