Summary
This online utility takes HTTP GET requests - written as a single URL - converts them to HTTP POST requests, and sends them to the needed Web server.
What are GET and POST requests?
You can find a fairly clear, rigorous and concise explanation at W3School's HTTP methods GET vs POST in the section Compare GET vs. POST.
What's the reason to use HTTP POST Relayer?
The submission of online forms is usually done thru GET requests and URLs, but you can stumble upon POST forms on the web. Their annoyance is that, after a form submission, the landing page's URL has no indication of the generating query. In the case you need to save the query, for later use or for sharing the result with other people, there is no way to do it.
HTTP POST Relayer makes it possible. It takes a special GET request/URL, reshapes it as a POST request, and sends it to the needed site. The target Web server will be unaware of what happened behind the scenes, and sends you back the correct reply page.
Thanks to HTTP POST Relayer, normal plain-text links may thus store within themselves all the query arguments used in a POST request and can execute the needed POST request.
How to create working / shareable POST links
See the additional section Direct use: normal links are able to contain and manage a POST request on the fly, without the need to open this page and paste manually the URL. These automatic links can be shared, written down in texts and references, or saved as bookmarks in your browser.
Direct use
The full URL to be converted can be appended just after the URL of this site!
Full syntax is: + "?" + server location + path (if needed) + "?" + arguments (postvar1=value1&postVar2=value2&...)
Example: .
Click on the above link to check and see how it works.
Normal links can now act as POST requests with their arguments. They can be cited in texts or saved as bookmarks.