buildfailingversion0.6.1licenseMIT
GetPostBridge sends an HTTP POST for clients that can only make a GET: link checkers,
feed readers, spreadsheet import functions, a browser's address bar, tools that are handed a URL and nothing
else. The request is written into a link. Fetching the link sends it.
This is the demo instance. It runs whatever is on the main branch and restarts when it feels like it.
Quick start
No install, no key. Fetch this:
https://www.getpostbridge.com/v1/relay?url=https%3A%2F%2Fexample.com%2Fapi&json=%7B%22name%22%3A%22test%22%7D
or let curl do the encoding:
curl -G https://www.getpostbridge.com/v1/relay --data-urlencode 'url=https://example.com/api' --data-urlencode 'json={"name":"test"}'
Reference
GetPostBridge: Send a POST with a GET
Fetch a link that names the address and the body. This sends
{"name":"test"} to https://example.com/api as a POST:
https://www.getpostbridge.com/v1/relay?url=https%3A%2F%2Fexample.com%2Fapi&json=%7B%22name%22%3A%22test%22%7D
With curl, which does the encoding for you:
curl -G https://www.getpostbridge.com/v1/relay --data-urlencode 'url=https://example.com/api' --data-urlencode 'json={"name":"test"}'
The answer is JSON. "downstream" is what the other side said:
{"outcome":"completed","downstream":{"status":200,"body_bytes":15,"redirect_followed":false,"content_type":"application/json","body":"{\"ok\":true}"},"replayed":false}
json=... goes out as application/json. payload=... goes out as
text/plain, or as whatever content_type=... says. format=text gives
the body alone, with the status in X-Relay-Downstream-Status.
The same link fetched twice sends once: the second answer is the first
one again, with "replayed":true. To send it again on purpose add
idempotency_key=<a word of your own> and change the word. A redirect
is not followed; the 3xx is the answer. method=... sends something
other than a POST, headers=<a JSON object> adds headers. No key, no
account.
Try the demo
This form builds the link for you and opens it.
Good to know
- A link that sends a request sends it for whoever opens it. Do not paste one where a crawler or a chat preview will find it unless that is what you want.
- Only public addresses. It will not reach into anybody's network, ours included.
- What the other side answers comes back whole: its status, its type and its body.
Run your own
Unpack a release, then:
$ cd getpostbridge $ ./configure.sh # asks for a port $ ./run.sh
Docker image: TODO.
Changelog
| 0.6.2 | Fixes a crash on an empty address. Addresses without a scheme are taken as http. |
|---|---|
| 0.6.1 | Headers of your own. |
| 0.6.0 | Methods other than POST. |
| 0.5.0 | First public demo. |