Yup. @john.spurlock already reported 1 & 2. I think I mentioned earlier we're not doing #4 until after open beta

Range support checking should be done by looking at the

Accept-Ranges

header in the response

MDN doesn't have

bytes=0-

documented - need to see if it's part of the spec

Ah found it

Ok, so I have absolutely no idea what is going on here. If I PUT an object with

await env.R2.put(key, request.body, {httpMetadata: {cacheControl: 'max-age=86400'}})

, something really, really weird is happening with the HTTP metadata... PUT result:

"httpMetadata":{"cacheControl":"max-age=86400"}

- yup, this looks right HEAD result:

"httpMetadata":{"contentDisposition":"max-age=86400"}

- this is not the right header 🤔 GET result (S3-compatible API):

content-language: max-age=86400

- the header changed again???

So my

cacheControl

can turn into

Cache-Control

,

Content-Disposition

or

Content-Language

depending on where I request the object.

@Vitali is this something you've experienced before?

That is definitely very strange and unexpected. I'll need to take a look

get and head being different is even weirder

Just note the GET is from S3 API

HEAD is from a Worker binding

PUT is the return value of the above statement

Will have to investigate it later today

PSA: R2 production will be going down for ~5-10 minutes in the next ~10 minutes.

HEAD/GET with bindings both return Content-Disposition. HEAD/GET with S3-compatible API both return Content-Language.

Oh, no, my logpush job 😢

Perf improvements incoming? 👀

Is there a better time to take it down?

Nah, was just making fun. That logpush job is for a testing domain, so there's no issues at all 🙂

wouldn't put anything production-critical on R2 yet

ETA for being back up is ~2 min

Looks to be up again

It may take a while for the change to propagate

So there may be a few more minutes of downtime for some

Currently ETA ~3 min for full restoration

@albert can you turn off your logpush for a couple of minutes?

Seems like your account hasn't refreshed

Actually maybe a different albert

I'm

e5f0f929bb59b9d5e1bc9b35e9e3bf00

Yeah that is you