UAE Broken Proxys - how to work around them

In the UAE there is a goverment enforcement of all traffic to go through goverment proxy servers. All requests are proxied and cached. What does this mean in the mysql world? Imagine you have a web application that records comments to a media object. Then a single person from the UAE makes a comment to that media object. The UAE Cache Proxy caches the HTTP-POST. Now every person in the country that visits your domain causes a HTTP-POST to that same media object. From a outside view it looks like content is being added to the system and the numbers are good. But ALL THE CONTENT is the SAME which is not valuable to the media owner nor the DBA who has to manage that data due to the BROKEN-CACHE-PROXY.

So how do you bust the BROKEN-CACHE-PROXY?

A simple method is to look at the contents of the last few posts and see if the same data is being added prior to insert-but this can be expensive at high scale-the scale that I deal with (billions of transactions per day).

A simple approach is to just add a hidden variable to the POST with your webservers time. If you webserver time on the post >= hidden variable time + 120 seconds then you know its a bad post.