Skip to content

Commit dd151d3

Browse files
Refine BFF pipeline diagram for clarity, update Mermaid syntax, and improve consistency in middleware descriptions.
1 parent 384574e commit dd151d3

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

astro/src/content/docs/bff/architecture/multi-frontend.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -73,15 +73,15 @@ BFF V4 still allows you to manually configure the ASP.NET Core authentication op
7373
To achieve this, the BFF automatically configures the ASP.NET Core pipeline:
7474

7575
```mermaid
76-
%%{ init: { 'theme': 'default' } }%%
76+
---
77+
title: BFF Middleware Pipeline
78+
---
7779
flowchart TD
78-
A["1. FrontendSelectionMiddleware"] --> B["2. PathMappingMiddleware"]
79-
B --> C["3. OpenIdCallbackMiddleware"]
80-
C --> D["4. Your application's ASP.NET Core pipeline"]:::app
81-
D --> E["5. MapRemoteRoutesMiddleware"]
82-
E --> F["6. ProxyIndexMiddleware"]
83-
84-
classDef app fill:#d5e8d4,stroke:#82b366
80+
A["FrontendSelectionMiddleware"] --> B["PathMappingMiddleware"]
81+
B --> C["OpenIdCallbackMiddleware"]
82+
C --> D["Your ASP.NET Core Pipeline"]:::app
83+
D --> E["MapRemoteRoutesMiddleware"]
84+
E --> F["ProxyIndexMiddleware"]
8585
```
8686

8787
1. `FrontendSelectionMiddleware` - This middleware performs the frontend selection by seeing which frontend's selection criteria best matches the incoming request route. It's possible to mix both path based routing and host based routing, so the most specific will be selected.

0 commit comments

Comments
 (0)