Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have the following situation;

  • a location only has a few hours of internet connectivity per day.
  • this location has however a functioning WiFi network to connect local machines

I need to have a local server that can for a specific web application

  • get POST requests and store them, waiting for internet connectivity to appear and then POST all those requests to the actual web server.
  • get GET requests and execute + cache them if there is internet connectivity, if there is no internet connectivity; use the cache

This solution would preferably run on Windows ( potentially old versions ) and would have to be free or open source. I am pretty much resigned to write something myself, but I would rather ask this community first.


share|improve this question

closed as not constructive by Greg Askew, Wesley, mdpc, Ward, John Gardeniers Dec 15 '12 at 10:02

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Sounds like you could use a transparent proxy (something like Squid) at the router level so that you don't need to worry about client compatibility. I don't know any kind of pre-fabricated solution that would store requests in a queue, though. It would not be too difficult to write from scratch. – Chris Kuehl Jun 1 '12 at 20:19

For GET requests a caching proxy could be configured to serve already cached data.

Most of the POST requests I work with depend a lot on how you navigated to them and are not really cachable in either direction. POST requests are often used in a sequence controlled by the server. This makes it extremely difficult to effectively store POST requests.

HTTP was not designed as a store and forward protocol. For simple GET requests, it is possible and often desirable to cache data to ease load on the network and servers. Other requests are often non-cacheable.

share|improve this answer
I know that HTTP ( especially POST ) was not designed for this, but I was hoping that someone else already had done this. I am planning to put the application logic in javascript without having a server side session so that only the last step is a POST. – tomdemuyt Jun 3 '12 at 3:57
I will not mark you answer as an answer, I am hoping that at some point there will be a ( new ) solution and then I will mark that answer as the one. I did +1 it. – tomdemuyt Jun 5 '12 at 17:33

Not the answer you're looking for? Browse other questions tagged or ask your own question.