You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The page at https://developers.cloudflare.com/r2/buckets/create-buckets/ stated that:
"The TLS (SSL) certificate created for each R2 bucket uses a wildcard certificate of the form *.r2.cloudflarestorage.com, which prevents account IDs and names from showing up in Certificate Transparency logs."
In reality, the certificates *do* contain the account ID, eg. "*.aaaaaabbbbbbccccccc.eu.r2.cloudflarestorage.com" is included in the certificate.
- Bucket names and buckets are not public by default. To allow public access to a bucket, [visit the public bucket documentation](/r2/buckets/public-buckets/).
50
50
- Invalid (unauthorized) access attempts to private buckets do not incur R2 operations charges against that bucket. Refer to the [R2 pricing FAQ](/r2/pricing/#frequently-asked-questions) to understand what operations are billed vs. not billed.
51
-
- The TLS (SSL) certificate created for each R2 bucket uses a wildcard certificate of the form `*.r2.cloudflarestorage.com`, which prevents account IDs and names from showing up in Certificate Transparency logs.
0 commit comments