Last-Modified vs. Raven-Last-Modified

[Tobi]

Looking at some raw data today, I noticed, I now have two Last-Modified
fields in the metadata:

"Last-Modified": "2013-10-14T15:24:00.8886718Z",
"Raven-Last-Modified": "2013-10-14T15:24:00.8886718",

I've read a thread about RFC1123 vs ISO8601 in the HTTP header, but why
is the same value *stored* twice? On small documents this can be an up
to 20% increase in size.

Can it actually happen that Last-Modified is != Raven-Last-Modified ?

BTW: It would also be nice to get rid of

"Non-Authoritative-Information": false

Tobias

[Oren Eini (Ayende Rahien)]

It isn't actually stored, and neither is the non authortative header

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tobi]

Sorry, my fault. I've just looked at my backed up Json, which contains
*all* the metadata returned via the client interface.

Tobias

Am 21.07.2014 13:50, schrieb Oren Eini (Ayende Rahien):

> It isn't actually stored, and neither is the non authortative header
>
> On Jul 21, 2014 1:50 PM, "Tobi" <lista...@e-tobi.net

> <mailto:lista...@e-tobi.net>> wrote:
>
> Looking at some raw data today, I noticed, I now have two
> Last-Modified fields in the metadata:
>

> "Last-Modified": "2013-10-14T15:24:00.8886718Z"__,

> "Raven-Last-Modified": "2013-10-14T15:24:00.8886718",
>
> I've read a thread about RFC1123 vs ISO8601 in the HTTP header, but
> why is the same value *stored* twice? On small documents this can
> be an up to 20% increase in size.
>
> Can it actually happen that Last-Modified is != Raven-Last-Modified ?
>
> BTW: It would also be nice to get rid of
>

> "Non-Authoritative-__Information": false

>
> Tobias
>
> --
> You received this message because you are subscribed to the Google
> Groups "RavenDB - 2nd generation document database" group.
> To unsubscribe from this group and stop receiving emails from it,

> send an email to ravendb+unsubscribe@__googlegroups.com
> <mailto:ravendb%2Bunsu...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/__optout
> <https://groups.google.com/d/optout>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "RavenDB - 2nd generation document database" group.
> To unsubscribe from this group and stop receiving emails from it, send

> an email to ravendb+u...@googlegroups.com
> <mailto:ravendb+u...@googlegroups.com>.