Correct Content-MD5 validation #97

Closed
seancribbs opened this Issue Jan 30, 2013 · 1 comment

1 participant

@seancribbs
Webmachine member

Apparently, as outlined in basho/webmachine#117, the header is actually supposed to be base64-encoded. We should correct this.

@seancribbs
Webmachine member

See also basho/webmachine#116

@bernd bernd referenced this issue Jul 18, 2013
Merged

Release 1.2.0 #111

@ghost Unknown added a commit that referenced this issue Feb 8, 2014
Robert Gleeson decode 'Content-MD5' checksum as base64-encoded string.
in the RFC the header is defined as:

        Content-MD5   = "Content-MD5" ":" md5-digest
        md5-digest   = <base64 of 128 bit MD5 digest as per RFC 1864>

closes #97
9c777b7
@ghost Unknown added a commit that referenced this issue Feb 8, 2014
Robert Gleeson decode 'Content-MD5' checksum as base64-encoded string.
in the RFC the header is defined as:

        Content-MD5   = "Content-MD5" ":" md5-digest
        md5-digest   = <base64 of 128 bit MD5 digest as per RFC 1864>

closes #97
7d88df6
@ghost Unknown added a commit that referenced this issue Feb 10, 2014
Robert Gleeson decode 'Content-MD5' checksum as base64-encoded string.
in the RFC the header is defined as:

        Content-MD5   = "Content-MD5" ":" md5-digest
        md5-digest   = <base64 of 128 bit MD5 digest as per RFC 1864>

closes #97
6190a28
@ghost ghost closed this in #149 Feb 10, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment