How Devflare wires mTLS Certificates from config to runtime
mTLS certificate bindings let a Worker make outbound fetches with a client certificate.
mTLS Certificates compiles from to Wrangler , with local/test behavior called out explicitly.
Use this page when you need emitted config, preview behavior, or Cloudflare-specific limits. The overview and example pages stay focused on everyday app code.
- Normalization
- Devflare normalizes before emitting Wrangler
- Compile target
- Wrangler
- Preview note
- Real TLS client-certificate presentation is Cloudflare/Wrangler remote behavior.
How authored config becomes Wrangler config
The authored config stays camelCase and project-oriented. The compiler translates that into the Wrangler keys Cloudflare expects.
The emitted output is shown here so the usage pages do not have to explain compiler details.
mTLS Certificates config and emitted Wrangler output
Use this when you need to check how the Devflare config becomes Wrangler-compatible config.
What local runtime support covers
- Offline-fixture: local tests can model Fetcher behavior, but not real certificate presentation
- The default docs recipe uses with .
- Pure unit tests can use / when the test only needs deterministic application behavior.
Compile, preview, and cleanup behavior
- Devflare emits Wrangler from the native config surface.
- Preview and deployment lifecycle stay feature-specific; do not assume all Cloudflare products can be created, cloned, or cleaned up the same way.
- Real TLS client-certificate presentation is Cloudflare/Wrangler remote behavior.
Cloudflare docs vs the Devflare layer
Cloudflare mTLS docs is the platform reference. Use this internals page when you need to compare Cloudflare's product docs with Devflare config, generated env types, local support, and preview behavior for .
| Question | Cloudflare docs | This Devflare page |
|---|---|---|
| Primary focus | Platform reference for mTLS certificate bindings and certificate-backed outbound fetches. | How to author , what the runtime surface looks like, and how mTLS Certificates fits a Devflare project. |
| Testing and runtime lens | Cloudflare’s docs focus on the raw binding API, product semantics, and platform limits for the binding itself. | Offline-fixture: local tests can model Fetcher behavior, but not real certificate presentation. Use the Devflare guidance when you need the honest local harness or the right remote gate instead of only the product API shape. |
| When to open it | When you need the platform contract, limits, APIs, or account-level product details. | When you are wiring, testing, previewing, or reviewing the binding inside a Devflare app. |
Previous
mTLS Certificates
Add the mTLS Certificates config, call from worker code, and start with the local test path Devflare supports.
Next
Testing mTLS Certificates
Test mTLS Certificates by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.