That's what I figured

Can you build on top of that PR until it works? I gotta go get some dinner

One of x-amz-date and date is required by the spec

To make sure there's no replay attacks

well the thing is that it is there

Must be an invalid format

That's very strange

when i look at the docs () it gives an example of

20150830T123600Z

which seems to be the same format as that one above as far as i can tell?

Yup

Here's where the code you're hitting is:

let requestDate = request.headers.get('x-amz-date')
  let dateOrigin: 'x-amz-date' | 'date' = 'x-amz-date'
  if (!requestDate) {
    // x-amz-date takes precedence over date
    requestDate = request.headers.get('date')
    if (!requestDate) {
      return errors.invalidArgument(
        { account },
        'No date provided in x-amz-date nor date header',
      )
    }
    dateOrigin = 'date'
  }

I don't know what's going on (pretty sure the get is case insensitive)

can you redo the request again?

redone

Here's what wrangler tail is showing me:

"method": "PUT",
      "headers": {
        "accept-encoding": "gzip",
        "cf-connecting-ip": "<REDACTED>",
        "cf-ipcountry": "GB",
        "cf-ray": "70447d9d3f3276d8",
        "cf-visitor": "{\"scheme\":\"https\"}",
        "connection": "Keep-Alive",
        "content-length": "10",
        "content-md5": "sFQDISxmvcjMxZf+32zV/g==",
        "content-type": "text/plain; charset=utf-8",
        "host": "<REDACTED>.r2.cloudflarestorage.com",
        "user-agent": "rclone/v1.59.0-beta.6112.3f5bed51d.fix-missing-sigv4-header",
        "x-amz-acl": "private",
        "x-amz-content-sha256": "UNSIGNED-PAYLOAD",
        "x-amz-meta-mtime": "1651242675.438993951",
        "x-forwarded-proto": "https",
        "x-real-ip": "<REDACTED>"
      },

thats my IP address :P but yes thats the same as what im seeing too from mitmproxy

Don't know what's happening, but that x-amz-date header isn't making it into R2

I thought you said they were sending it?

You missed one at the bottom 🙂

x-amz-date

isn't there

oh wait no its not the same as what im seeing my bad

Maybe the mitmproxy strips it. Or maybe it's some middleware on our end.

mitmproxy gives me

X-Amz-Algorithm:     AWS4-HMAC-SHA256
X-Amz-Credential:    redacted/20220501/us-east-1/s3/aws4_request
X-Amz-Date:          20220501T004441Z
X-Amz-Expires:       900
X-Amz-SignedHeaders: content-md5;content-type;host;x-amz-acl;x-amz-meta-mtime
X-Amz-Signature:     redacted

its the same symptom without mitmproxy, just tried

X-Amz-Credential

isn't a thing though

That's part of the

Authorization

header

FML. That's presigned

oh wait wait hang on i get it now

its sending X-Amz-Date as a query

We don't support presigned yet