which date does the browser send ? you would expect the last-modified date from
the same request, but there is no get ? still puzzling for me. and don't you
use these headers for concurrent modification/optimistic updates normally ?
--
http://r
On Tue, Sep 4, 2012 at 8:21 AM, Koen Maes wrote:
> It is indeed a edge case where you have a POST and no get.
By "edge case", I was referring not to the practice of having POST-only
resources (which isn't at all unusual) but to the presence of an
If-Modified-Since header in a request to such a
Ok, my mistake not If-none-match but if-modified-since
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3003440
It is indeed a edge case where you have a POST and no get. I wonder where the
browser gets its ETAG from then ???
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3003438
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 hav
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
6 matches
Mail list logo
