mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-05 05:42:16 +00:00
* docs(manage): add production checklist * chore: add tracing to defaults * fix links * fix links * link custom domain page * Update docs/docs/guides/deploy/overview.mdx Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/deploy/overview.mdx Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/deploy/overview.mdx Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/deploy/overview.mdx Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/manage/self-hosted/production.md Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/manage/self-hosted/production.md Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/manage/self-hosted/production.md Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/manage/self-hosted/production.md Co-authored-by: Florian Forster <[email protected]> * Update docs/docs/guides/manage/self-hosted/production.md Co-authored-by: Florian Forster <[email protected]> * fix typos * link to metrics page * link to projections concept * chore(docs): format docs * visually add spaces * use explicit line breaks * fix italic underscores * reuse .prettierignore * cd to docs * ignore generated .md files * pin prettier version * format non docs markdown files * fix glob file pattern * fix glob file pattern * fix glob file pattern * enforce prose wrap * fix italic env vars * use .prettierrc.yaml * use folder specific configs * fmt docs and md in other branch Co-authored-by: Florian Forster <[email protected]>
16 lines
1.1 KiB
Plaintext
16 lines
1.1 KiB
Plaintext
---
|
|
title: HTTP/2 Support
|
|
---
|
|
|
|
ZITADEL follows a strict API first approach and makes heavy use of the modern API framework called [gRPC](https://grpc.io/).
|
|
Besides gRPC all APIs are also available in an openapi Rest fashion as well as in gRPC-web for compatibilty towards browser integrations.
|
|
|
|
To make us of gRPC it is vital to allow your clients to communicate with ZITADEL with [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2).
|
|
|
|
Sometimes you need to configure explicitly that you want to use HTTP/2 if you run ZITADEL behind a reverse proxy and below you should find examples for different vendors and projects.
|
|
|
|
Furthermore it is important to notice that by default HTTP/2 is always encrypted, but if you want to run ZITADEL without TLS from your reverse proxy or service mesh this is possible through [h2c](https://httpd.apache.org/docs/2.4/howto/http2.html).
|
|
Oftentimes when you run ZITADEL inside a service mesh, or a servelerss offering (e.g. Google Cloud Run, Knative, ...) you will need h2c.
|
|
|
|
You can read more about ZITADEL's [TLSs modes here](/docs/guides/manage/self-hosted/tls_modes).
|