I'm sure everyone agrees that conditional GET and PUT are essential tools. Restlet's support for these is one of the things that drew me to Restlet in the first place.
But the original question was about conditional POST (if-modified-since header in POST request). What does it mean? Unless you have defined your own semantics for this, you'll want to ignore conditional headers in POST requests, and my response describes a simple way to do so in Restlet in the edge case where a resource does not support GET. --tim On Tue, Sep 4, 2012 at 5:13 AM, Koen Maes <k...@koma.be> wrote: > I do not feel it is a mistake that browsers exhibit this behaviour, on the > contrary. > > I have asked a similar question in this forum before, on how to work with > ETag and wether I had to manage a cache of my own and verify with the > server for 304's. > > The given behaviour, it turns out, I just don't have to care. I do a first > GET request to the server, and the server responds back with an ETAG. Upon > the next request to the same URL (and no params!), I do not have to keep > the previous version around. The browser takes it from disk cache and sends > the If-modified header to the server, receives the 304, and returns the > entity from disk. No code needed, use the power of the browser. > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3003392 > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3003415
