This can be improved by an experimental feature called Orange-to-Orange (O2O) from the Cloudflare Edge team. O2O allows one zone on Cloudflare to CNAME to another zone, and apply the settings of both zones in layers. For example, cloudflare-ipfs.com has Always Use HTTPS turned off for various reasons, which means that every site served through our gateway also does. O2O allows site owners to override this setting by enabling Always Use HTTPS just for their website, if they know it’s okay, as well as adding custom Page Rules and Worker scripts to embed all sorts of complicated logic.
This is a feature we really need enabled but I don’t see an option on my dashboard to join beta test for O2O. Is it possible for my account to be included in the O2O beta test? Thanks!
Hey @domjh, thanks for the response. We are not on Enterprise. Since the post is from 2019, is it still the case today that only Enterprise customers can have this additional feature?
We dont allow O2O to cloudflare-ipfs.com. Thats an old blog and is out of date, it appears. I would suggest raising a Feature Request along the lines of “Ability to configure {features here} on traffic to my IPFS Gateway”.
@smarsh I could be wrong here but it looks like app.uniswap.org has cloudflare-ipfs.com as CNAME and they’re able to do url rewrites (any path maps back to index.html). The uniswap domain nameservers are Cloudflare. Do you know how it’s possible to do url rewrites without O2O like how uniswap is doing it? We’re trying to achieve the same thing. Thanks!
To be able to cover non existing or other paths, setup a worker on the client side to proxy requests. That is the current recommendation until we officially support O2O for IPFS, which is definitely on the roadmap.