6 messages in ru.sysoev.nginxRe: Will nginx support HTTP Etag ?
FromSent OnAttachments
Xia QingranApr 14, 2009 2:33 am 
Anton YuzhaninovApr 14, 2009 3:04 am 
Michael ShadleApr 14, 2009 8:36 am 
Xia QingranApr 14, 2009 7:53 pm 
Phillip B OldhamApr 15, 2009 12:37 am 
Anton YuzhaninovApr 15, 2009 2:51 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Will nginx support HTTP Etag ?Actions...
From:Anton Yuzhaninov (cit@citrin.ru)
Date:Apr 14, 2009 3:04:04 am
List:ru.sysoev.nginx

Xia Qingran wrote:

After reading http://wiki.nginx.org, I find out that nginx has not the offical support for the HTTP Etag, http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.19 . I want to know whether the future version of nginx will add this feature.

My website is taking use of nginx to run static files server including lots of Javascipt and CSS files modified frequently. Now I set a very short expires time like, expires 1h, to renew the client cache as soon as possible.

But I think it is not a good solution. It wastes my network bandwidth if I do not modify the static files.

If last-modifed date of file is not changed, bandwidth saved:

client send in request

header If-Modified-Since:

and if time in request same as time of file modification on disk nginx send
reply HTTP/1.x 304 Not Modified

In general Etag for static files is not better than Last-Modified header.

Etag is useful for dynamic content, when modify time is not known. In this case
Etage can be generated from hash (md5/sha) of content.