Set Content-MD5 only if ETag has correct format

Previously this check was more lenient than it should have been.
We're inverting the logic here (was `!...matches()`) - is that intentional? Also dropping support for etags of the form "AAAA-1111"...is that OK?