Bundle methodologies
import { Tabs, TabItem } from "~/components";
When an SSL certificate is deployed to Cloudflare's global network, it may be augmented with intermediate and root certificates to assist the user agent in finding a chain to a publicly trusted root.
You can control the mechanics of how certificates are bundled by specifying a bundling methodology.
Intermediate and root certificates
Cloudflare maintains intermediate and root certificates used for bundling on a GitHub repository. As the certificates expire or are removed by certificate authorities, Cloudflare removes and adds them accordingly.
Expiration values for these certificates may appear in the expires_on field when you use the Analyze Certificate endpoint - often when the methodology you specify is Compatible. However, these expiration values reflect intermediate and root certificates - which are handled by Cloudflare -, not the leaf certificate you would have previously uploaded to Cloudflare.
:::note
When using compatible or modern, a selection might be done on the intermediates you provide at upload time, meaning it is not guaranteed all of them will make it to the final chain. If you must ensure the chain you upload is the one used, select user-defined.
:::
Methodologies
Compatible
Compatible is the default methodology and uses common and well distributed intermediate certificates to complete the chain. This ensures that the resulting bundle is compatible with as many clients as possible.
Modern
Modern consists of attempts to make the chain as efficient as possible, often by using newer or fewer intermediate certificates.
User-defined
User-defined allows you to paste your own certificate chain and present that bundle to clients. If you are using a self-signed certificate (not recommended), you must use this mode.
谢谢你的反馈！