checksum - GitHub raw files - Etag algorithm -
does know how github etag when accessing raw content generated?
as far can tell not md5, sha1 or common sha variant;
example http headers:
http/1.1 200 ok server: nginx/1.0.13 date: tue, 05 jun 2012 19:46:08 gmt content-type: text/html; charset=utf-8 connection: keep-alive status: 200 ok etag: "aa1da178ae0a43e23ce49a6b8f474738" the etag length 32 characters, suggesting md5, not match md5 checksum of downloaded file (downloaded using curl).
i aware etags should treated opaque identifiers. still, curious.
my guess using stock nginx etag module.
https://github.com/mikewest/nginx-static-etags/blob/master/ngx_http_static_etags_module.c
Comments
Post a Comment