On single-digit days (like today), rfc822Time produces a Date header like this:
Date: Tue, 8 Nov 2016 20:50:14 GMT
with two spaces between the comma and 8. Google's XML API rejects this, saying that a header is malformed. It seems they are being very strict in their interpretation of the RFC - if I'm reading it correctly, it specifies a comma, single space and one or two digits after that.
Anyway, changing the space to a zero seems to fix it. I checked that this does not break Amazon's S3, but didn't try any other services.
On single-digit days (like today), rfc822Time produces a Date header like this:
with two spaces between the comma and 8. Google's XML API rejects this, saying that a header is malformed. It seems they are being very strict in their interpretation of the RFC - if I'm reading it correctly, it specifies a comma, single space and one or two digits after that.
Anyway, changing the space to a zero seems to fix it. I checked that this does not break Amazon's S3, but didn't try any other services.