We are debating whether to use the Content-MD5 header.
- The CMS allows us to easily include it with minimal overhead (cached responses in 80%+ of the cases).
- It would add another layer of protection against problems.
- The Content-Length header is always present (even on dynamically created pages) so the client should not need another form of validation.
- So far we are unaware of any problems caused by corruption.
- MD5 checks add latency to web page load times.
- Do certain media types include their own form of digest that makes this unnecessary?
- If TCP offers this already why was it included in the HTTP standard?
- What are the existing real-life uses?
- Is the MD5 check negligible?
It is no real problem for this to be added to the unit tests and implemented, about an hours work; however if it is detrimental then we want it added to the higher level sniff tests used in website "health check"s.