Data is single region currently but you can use cache to enhance warm reads.
Data is single region currently but you can use cache to enhance warm reads.
https://dev.name-of-my-app.com just fine.localhost to the prod bucket just fine. BUT, when I try to PUT from https://app.name-of-my-app.com, I get a 403 CORS error like this...https://app.name-of-my-app.com does not even though it's in the AllowedOrigins array. Appreciate any help y'all have.SignatureDoesNotMatch then it isn't a failure due to CORS, it would have failed anyways.app.name-of-my-app.com , which is pointing to the same server as localhost, and when I PUT to the presigned URL, there is a 403.rclone. What's the time unit of rclone link --expire? Is it seconds?d at the end, for example --expire 1d becomes 86400 seconds (1 day) whereas --expire 1 is 1 second


https://dev.name-of-my-app.com[
{
"AllowedOrigins": [
"http://localhost:3000",
"https://dev.name-of-my-app.com"
],
"AllowedMethods": [
"PUT",
"GET"
],
"AllowedHeaders": [
"*"
]
}
][
{
"AllowedOrigins": [
"http://localhost:3000",
"https://app.name-of-my-app.com"
],
"AllowedMethods": [
"PUT",
"GET"
],
"AllowedHeaders": [
"*"
]
}
]https://app.name-of-my-app.comhttps://app.name-of-my-app.comAccess to XMLHttpRequest at 'https://...r2.cloudflarestorage.com/path/to/uploaded/file.txt?X-Amz-Algorithm=...' from origin 'https://app.name-of-my-app.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.AllowedOriginsSignatureDoesNotMatch<Error>
<Code>SignatureDoesNotMatch</Code>
<Message>The request signature we calculated does not match the signature you provided. Check your secret access key and signing method. </Message>
</Error>app.name-of-my-app.comrclonerclone link --expire?d--expire 1d--expire 1