We have recently been using vault.revera.co.nz and noticed that it stopped working for us yesterday at 1st Nov at 00:00:0 GMT. To fix it we changed the format of the date in the signed string from.
Tue, 1 Nov 2016 03:56:43 GMT
to
Tue, 01 Nov 2016 03:56:43 GMT
This seemed to fix it, but we are not sure why. My hunch is that vault.revera.co.nz does not canonicalise the date it finds in the headers (where aws does include a leading 0).
The quick fix we used is here, but if the current version is working with AWS this would likely break it (unless they accept signatures for both possible strings). A better fix might be to change the format of the Date header to match what is in the signed string.
We have recently been using vault.revera.co.nz and noticed that it stopped working for us yesterday at 1st Nov at 00:00:0 GMT. To fix it we changed the format of the date in the signed string from.
to
This seemed to fix it, but we are not sure why. My hunch is that vault.revera.co.nz does not canonicalise the date it finds in the headers (where
awsdoes include a leading 0).The quick fix we used is here, but if the current version is working with AWS this would likely break it (unless they accept signatures for both possible strings). A better fix might be to change the format of the Date header to match what is in the signed string.