Skip to content

Commit 72b51ee

Browse files
Merge pull request mendix#9780 from pommi/mendix-cloud-request-headers-case-insensitive-header-names
mendix-cloud-request-headers: case-insensitive header names
2 parents 48443da + d624dd1 commit 72b51ee

2 files changed

Lines changed: 12 additions & 0 deletions

File tree

content/en/docs/deployment/mendix-cloud-deploy/mendix-cloud-request-headers.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,18 @@ Most of the request headers are added by the HTTP client (the web browser, for e
1818

1919
Using custom Java code in the application, the full content of an incoming request can be inspected.
2020

21+
Request header names are case-insensitive, as defined by [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2). This means that headers such as `X-Header-Key`, `x-header-key`, and `X-HEADER-KEY` must be processed in the same way.
22+
23+
When processing request headers, Mendix recommends converting all request headers names to lowercase to account for case-insensitivity. For example:
24+
25+
```bash
26+
toLowerCase($HeaderKey) = 'x-header-key'
27+
```
28+
29+
This ensures consistent handling regardless of the casing used in incoming requests and supports compliance with HTTP standards.
30+
31+
{{< figure src="/attachments/deployment/mendix-cloud-deploy/mendix-cloud-request-headers/tolowercase-header-name.png" alt="Lowercase Request Header Names" width=50% >}}
32+
2133
### Usually Available Request Headers Set by the HTTP Client
2234

2335
The following headers are usually set by the HTTP client. Mendix Cloud does not touch the value of these headers. This also means that they might not be available if the HTTP client does not set them.
43.5 KB
Loading

0 commit comments

Comments
 (0)