The fact that I am getting feature requests means people are actually using my post test server. This makes me happy :) The most recent thing people asked for was multipart/form-data uploads. As an example for this behavior see my test form (which was submitted by a user who was super helpful).
<form action="http://posttestserver.com/post.php?dir=example" method="post" enctype="multipart/form-data">
File: <input type="file" name="submitted">
<input type="hidden" name="someParam" value="someValue"/>
<input type="submit" value="send">
The resulting output should contain information about the file and a link to the actual uploaded file. Remember, this data is public and you should NOT upload private data.
Based on feedback, I’ve added an HTTPS certificate to http://www.posttestserver.com. You may now access the site from: https://posttestserver.com. Hopefully this helps some people.
Today, the system worked! I received an email from a user asking if I could add support for custom status codes to Post Test Server and I was happy to oblige. So I have added a new parameter which can be passed in the URL called: status_code which causes the server to return a response with the header set to: HTTP/1.0 $status Custom Status (where $status is the value of status_code). Regardless of what code is requested the post will still be dumped in folder in the usual way.
To make it very clear, hitting this url:
will cause the server to respond with HTTP/1.0 650 Custom Status.
A while ago I put together a very simple php script that dumps any HTTP Post it receives:
To my great surprise, people have actually started using it! I also found myself using it more and more in my own debugging and so I have added two features which further my original mission of maximizing this project’s value to effort ratio. Total effort is still under one hour.
- Now dumps all Header parameters. Previously I was only dumping the ones that I thought relevant. Now you can see carrier and ISP inserted fields as well.
- You may now specify a directory in the query string to have your post written there. So instead of hitting: http://posttestserver.com/post.php you instead hit: http://posttestserver.com/post.php?dir=myself and then after selecting the current date you will see a myself directory containing your uploads
Hopefully this continues to help people. Even if it doesn’t, it helps me so I’m satisfied.
This past week I found myself writing code that had to submit some data to a webservice via an HTTP POST request. Not a particularly difficult task but it was on a platform I didn’t have much experience with and I wasn’t sure if I had formed the packet properly. In order to validate my bits I wrote a small php page which accepts POST requests and dumps them locally. Thanks to Dreamhost I’m now able to share this with everybody:
I’ll be slightly taken aback if anybody actually uses this thing, but when is that actually the point?
UPDATE: I added features!