<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Le 06/10/14 11:56, Albert Casademont
Filella a écrit :<br>
</div>
<blockquote
cite="mid:CAMA5aFYHgtF+7WkPtNzDhPVzNBvhrQrZKVLbTdo5p_P+xHt8Cw@mail.gmail.com"
type="cite"><br>
The weak etag preservation was added to nginx 1.7.3 so I guess
your problem is that you're still on the 1.6.* branch! Hope that
helps :)<br>
</blockquote>
Actually 1.4.6...<br>
<br>
$ aptitude show nginx-light<br>
Paquet : nginx-light <br>
État: installé<br>
Automatiquement installé: non<br>
Version : 1.4.6-1ubuntu3.1<br>
<br>
I'll upgrade I think...<br>
<br>
<br>
On the other matter, I'm rereading the relevant parts of the RFC to
see if the Etag vs Gzipping issue could be resolved... It's clear
that whenever the transmitted data changes, etag must change:<br>
<br>
A "strong entity tag" MAY be shared by two entities of a resource<br>
only if they are equivalent by octet equality.<br>
<br>
But also an identity-preserving Content-Enconding says just that: <br>
<br>
The Content-Encoding entity-header field is used as a modifier to
the<br>
media-type. When present, its value indicates what additional
content<br>
codings have been applied to the entity-body, and thus what
decoding<br>
mechanisms must be applied in order to obtain the media-type<br>
referenced by the Content-Type header field. Content-Encoding is<br>
primarily used to allow a document to be compressed <b>without
losing</b><b><br>
</b><b> the identity of its underlying media type</b>.<br>
<br>
<br>
So I think there's room for improvement.<br>
<br>
<br>
</body>
</html>