We are using the HTTP "Digest" header for checksums, which allows you to specify what type of algorithm is used (RFC 3230). "Content-MD5" is not used because it is limited to MD5.
Neil > > I was only aware of the Content-MD5[1][2] header actually. This header > contains the base64 encoded MD5 of the content after the header. > > I didn't know of the other check-sum methods you point to in the iana > document[3], and I'm not sure those make "Content-SHA", > "Content-UNIXsum" and "Content-UNIXcksum" valid as headers. > > My best guess would be that only "Content-MD5" in base64 encoded string > is valid. > > Bram > > > [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html > [2] http://www.ietf.org/rfc/rfc1864.txt > [3] http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml > > On Tue, 2009-09-29 at 01:17 -0700, Neil M. wrote: >> How is the describedby metalink mime type supposed to work? When we do >> the HTTP GET it is to retrieve a single file. A metalink file can >> describe multiple files. How does the client know which of the files in >> the referenced metalink file matches the GET request? >> >> >> Are SHA-256, etc. actually valid for the Digest header? The IANA >> document doesn't list them: >> >> http://www.iana.org/assignments/http-dig-alg/http-dig-alg.xhtml >> >> Can they be added to this list? >> >> Neil >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Metalink Discussion" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/metalink-discussion?hl=en -~----------~----~----~----~------~----~------~--~---
