The Last-Modified header is set when writing the object, so you cannot set it yourself. The ETag header is computed from various bits of metadata, so you can't control that either. I would discourage using these headers for conditional PUTs, but conditional GETs are just fine.
On Thu, Nov 28, 2013 at 2:03 AM, Georgio Pandarez <georgiopanda...@gmail.com > wrote: > Hi All, > > I'm investigating using Riak for a project and noticed that the HTTP > transport will supply an etag and last-modified header and will honour the > appropriate http if-modified-since request headers. > > Is there any way to control these values? I'd like the last-modified time > to be a value that I specify when adding the key etc. > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > > -- Sean Cribbs <s...@basho.com> Software Engineer Basho Technologies, Inc. http://basho.com/
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
