You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add support for forwarding proxy headers in template requests
- Updated `fetchTemplate` to include forwarded headers when fetching templates.
- Enhanced `wildcardRequestHandlerFactory` to forward template proxy headers.
- Modified `filterHeaders` to allow extra headers to be forwarded based on configuration.
- Introduced database migrations for new settings: `FragmentProxyHeaders` and `TemplateProxyHeaders`.
- Removed deprecated `fetch-template.js` and `filter-headers.js` files, refactoring their logic into new modules.
-**Locally configured Bearer token** for API machine-to-machine access. Default credentials: `Bearer cm9vdF9hcGlfdG9rZW4=:dG9rZW5fc2VjcmV0` or `Bearer root_api_token:token_secret` after base64 decoding.
-**Locally configured Bearer token** for API machine-to-machine access. Default credentials: `Bearer cm9vdF9hcGlfdG9rZW4=:dG9rZW5fc2VjcmV0` or `Bearer root_api_token:token_secret` after base64 decoding.
16
16
17
17
You can change default credentials via Registry UI, in the `Auth entities` page, or via API.
18
18
@@ -56,9 +56,9 @@ links to the JS/CSS bundles in the Registry after each deployment.
56
56
57
57
To do this, there are the following options (at least):
58
58
59
-
-Manually via UI (_not recommended_)
60
-
-Using Registry API (see [API](#api) section above)
61
-
-**Using App Assets discovery mechanism**
59
+
- Manually via UI (_not recommended_)
60
+
- Using Registry API (see [API](#api) section above)
61
+
-**Using App Assets discovery mechanism**
62
62
63
63
When registering micro frontend in the ILC Registry, it is possible to set a file for the "Assets discovery url" that will be periodically fetched
64
64
by the Registry. The idea is that this file will contain actual references to JS/CSS bundles and be updated on CDN **right after** every deployment.
@@ -195,3 +195,45 @@ Applications reference shared properties via the `configSelector` field.
195
195
### Domain properties
196
196
197
197
See [Multi-domains documentation](multi-domains.md#domain-specific-properties) for information about configuring domain-specific properties.
198
+
199
+
## Settings reference
200
+
201
+
ILC behavior can be tuned via the Settings page in Registry UI (`/settings`) or through the `PUT /api/v1/settings/:key` API.
A list of HTTP header names that ILC will forward from the incoming end-user request to **fragment SSR requests**. When ILC renders a micro-frontend server-side, the listed headers are copied from the browser request into the outgoing HTTP call to the fragment's SSR endpoint.
210
+
211
+
Headers are matched case-insensitively. Headers present in the list but absent from the incoming request are silently skipped.
212
+
213
+
**`null` (default)** — no extra headers are forwarded beyond the built-in set (see below).
214
+
215
+
**Built-in headers always forwarded to fragments** (regardless of `fragmentProxyHeaders`):
A list of HTTP header names that ILC will forward from the incoming end-user request to **template `<include>` fetches**. When the registry renders a template containing `<include src="…" />` tags, the listed headers are copied from the ILC→Registry request into the outgoing HTTP calls to each include source.
228
+
229
+
Headers are matched case-insensitively. Headers present in the list but absent from the incoming request are silently skipped.
230
+
231
+
**`null` (default)** — no extra headers are forwarded to include sources.
232
+
233
+
**Example — forward tracing and routing headers to both targets:**
234
+
235
+
```json
236
+
["x-forwarded-for", "x-real-ip", "x-request-id"]
237
+
```
238
+
239
+
**Caching note:** template rendering results (including fetched `<include>` content) are cached by ILC keyed on the template name, domain, and the forwarded header values. Forwarded headers are therefore expected to be **static per deployment context** (e.g. set by a reverse proxy, not by individual users). Using headers with many unique values (e.g. per-user auth tokens) will create a large number of cache entries and trigger LRU eviction — a warning is logged when this occurs.
0 commit comments