IPs just get you to Cloudflare, every server within Cloudflare handles your request. You could connect with a random IP found on Google and your site would still be served
What happens at Cloudflare and more likely the cause, your origin is unrelated.
Yeah, that would do it. Infrequent Access is almost always more expensive than Standard. Unless you have a huge R2 bill, you don't even need to consider IA. And even if then it's unlikely to save you much, if it all.
And don't expect for me to use this in my websites, I want my websites useable and my website literally works on 14 year old browser, I made my site work in mind with old versions.
I can't imagine they're going to revert, most websites build themselves in a way where they support a certain number of versions back for a browser, or do it based on usage %. It allows them to use modern features instead of being stuck in the past (or trying to polyfill everything) forever.
I have a custom wildcard SSL certificate , and I want to apply it only to abc.xyz.com while keeping all other subdomains under Cloudflare Universal SSL.
you cant create subdomain zones with just business plan, and creating a second zone as partial for the same domain doesnt work because a domain can only be on one zone at once regardless of type you need enterprise to create the subdomain zone for this
When you use a subdomain setup, you can manage the Cloudflare configurations for one or more subdomains separately from those associated with your apex domain. This means that, on your account homepage, you would find websites like example.com or blog.example.com listed as separate zones.
if all is well and total tls is working as designed, no but if a total tls cert fails to issue, fails to renew or otherwise goes missing / isnt ready yet, universal is used as a backup
if you want to guarentee the CA is always the same, issue a manual advanced cert for example.com and *.example.com, disable universal and use the manually issued one as the fallback instead