If it's a separate connection, then it's probably hitting a new colo and therefore it won't be cache
If it's a separate connection, then it's probably hitting a new colo and therefore it won't be cached.


/cli upload-file <file_path> <destination_file_path>?npm i s3. There are 330 other projects in the npm registry using s3.


wrangler r2 object put I suppose, but it only supports up to 315MB in size and there are other tools (rclone is one we recommend) to do more complex operations[
{
"AllowedOrigins": [
"https://anizium.com/",
"https://cdn.anizium.com/",
"https://static.anizium.com"
],
"AllowedMethods": [
"GET",
"POST",
"PUT"
]
}
]Request for Index 1
Request for File 1
Request for File 2
? Index 1 updated, contents change.
Request for File 3 -- maybe the wrong file.
Request for Index 1 (new changes, reset version)
Request for File 1 (new contents)/cli upload-file <file_path> <destination_file_path>npm i s3wrangler r2 object putrclone copy[
{
"AllowedOrigins": [
"https://anizium.com/",
"https://cdn.anizium.com/",
"https://static.anizium.com"
],
"AllowedMethods": [
"GET",
"POST",
"PUT"
]
}
]curl -s https://cloudflare.com/cdn-cgi/trace | grep -Eo "fl=(.\d)"