From 42cee0ed6c595eca7a43766ec571d2e04d7c59df Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Michaud?= Date: Mon, 12 Apr 2021 23:47:30 +0200 Subject: [PATCH] docs(proxy): clarify the workflow of a client request payload. (#1838) Fix #1836 --- docs/home/architecture.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/home/architecture.md b/docs/home/architecture.md index 7c7dd0987..5f6fc5783 100644 --- a/docs/home/architecture.md +++ b/docs/home/architecture.md @@ -12,7 +12,10 @@ It can be seen as an extension of those proxies providing authentication functio and a login portal. As shown in the following architecture diagram, Authelia is directly connected to -the reverse proxy but never directly connected to application backends. +the reverse proxy but never directly connected to application backends and therefore +the payloads sent by the clients of the protected API will never reach Authelia, only +the authentication pieces will, like the Authorization header for instance. Consequently, +the protected APIs can be a REST, a GraphQL or any other kind of API on top of HTTP.