Enter an issue title
Use SHA algorithm for content digest in URLUploader
Summary
Staging fails when running Diego and CAPI on a FIPS stemcell. The reason for this is that the URLUploader uses MD5 as content hashing algorithm.
CAPI has already been enhanced to support the Content-Digest HTTP header with the following format:
<algorithm>=:<base64-digest>:
As md5 is not available on FIPS stemcells, the algorithm used by the URLUploader should be one of the following: sha-512, sha-256 or sha-1.
See also cloudfoundry/cloud_controller_ng#3558
Diego repo
cloudfoundry/executor