I found that this was required. I am passing the Content-MD5 header from a node.js client app to a Rails 3.2.8 backend and it's ending up as HTTP_CONTENT_MD5 in Rails. It looks like other header fields have a check for the field name starting with HTTP as well, so it should make sense here as well.
I found that this was required. I am passing the Content-MD5 header from a node.js client app to a Rails 3.2.8 backend and it's ending up as HTTP_CONTENT_MD5 in Rails. It looks like other header fields have a check for the field name starting with HTTP as well, so it should make sense here as well.