Does anyone know how the GitHub ETag is generated when accessing raw content?
As far as I can tell, this is not MD5, SHA1, or any general 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 length of the ETag is 32 characters, which indicates MD5, but this does not correspond to the MD5 checksum of the downloaded file (downloaded using curl).
I know that ETags should be considered as opaque identifiers. However, curious.
Ishan source
share