http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/ $pithy_personal_mission_statement Wed, 19 Nov 2008 23:40:30 +0000 http://wordpress.org/?v=2.6.3 http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/#comment-65729 ed Mon, 30 Jun 2008 13:22:53 +0000 http://inkdroid.org/journal/?p=205#comment-65729 No I hadn't seen that <a href="http://gigaom.com/2008/06/27/storage-outages-can-todays-hardware-handle-the-cloud/" rel="nofollow">article</a>, thanks Andy! So is the benefit of using the Content-MD5 HTTP header in addition to the checks built in to TCP? It allows you to check the integrity of the transfer explicitly rather than implicitly by just using TCP? The header does seem redundant somehow--it would be interesting to know the history of why it was added. No I hadn’t seen that article, thanks Andy! So is the benefit of using the Content-MD5 HTTP header in addition to the checks built in to TCP? It allows you to check the integrity of the transfer explicitly rather than implicitly by just using TCP? The header does seem redundant somehow–it would be interesting to know the history of why it was added.

]]> http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/#comment-65560 Andy Boyko Fri, 27 Jun 2008 20:47:15 +0000 http://inkdroid.org/journal/?p=205#comment-65560 Did you see where they traced the corruption to a faulty load balancer? (Via <a href="http://gigaom.com/2008/06/27/storage-outages-can-todays-hardware-handle-the-cloud/" rel="nofollow">GigaOm</a>) Did you see where they traced the corruption to a faulty load balancer? (Via GigaOm)

]]> http://inkdroid.org/journal/2008/06/23/content-md5-considered-helpful/#comment-65401 Peter Murray Mon, 23 Jun 2008 20:26:32 +0000 http://inkdroid.org/journal/?p=205#comment-65401 Very interesting, indeed! I would have thought that the reliable transport of "TCP" was enough. Page 207 (section 13.14 "TCP Checksum Computation") of my trusty third edition of Comer's Internetworking with TCP/IP says "TCP uses 16-bit arithmetic and takes the one's complement of the one's complement sum. At the receiving site, TCP software performs the same computation to verify that the segment [headers plus playload] arrived intact." Very interesting, indeed! I would have thought that the reliable transport of “TCP” was enough. Page 207 (section 13.14 “TCP Checksum Computation”) of my trusty third edition of Comer’s Internetworking with TCP/IP says “TCP uses 16-bit arithmetic and takes the one’s complement of the one’s complement sum. At the receiving site, TCP software performs the same computation to verify that the segment [headers plus playload] arrived intact.”

]]>