yeah probably unlikely. btw a DO alarm should be easiest. can just set it to 1 year every time it's
yeah probably unlikely. btw a DO alarm should be easiest. can just set it to 1 year every time it's requested (we already route through Workers)
LastAccessed time to objects then are there any clients which will throw due to an unexpected key in the schema? But, like most R2 extensions to S3, they could just throw it in a custom header (or re-use Last-Modified).The specified bucket does not exist. (Code: 10006) error. I can create another custom domain on the bucket and it works fine.


/ as the valueput API. However, I keep getting "Provided readable stream must have a known length (request/response body or readable half of FixedLengthStream)" error. I have detailed a basic code example at https://gist.github.com/e332890143f40d1803a8d2aed089c517. Has anyone run into this and/or have a solution. Much appreciated!* to avoid them, but still seeing it intermittently. Only solution I've found so far is to "Disable cache" in the dev tools network tab, and that only works some of the time.

so this is basically a tradeoff between speed (less speed because of 1 extra API call), and cost (it will be cheaper because of Class A ops)export default <ExportedHandler<Environment>>{
async fetch(req, env) {
if (req.method === "POST") {
return Response.json(await env.R2.put("file", req.body));
}
return new Response((await env.R2.get("file"))?.body, {
headers: {
"content-type": "image/png"
}
});
}
}LastAccessedLast-ModifiedThe specified bucket does not exist. (Code: 10006)