2.2.33.56.3. Path normalization configuration examples
Ensuring Envoy normalizes request paths to match your backend services' expectations is critical to the security of your system. The following examples can be used as a reference for you to configure your system. The normalized URL paths, or the original URL paths if NONE is selected, will be:
- Used to check against the authorization policies.
- Forwarded to the backend application.
| If your application… | Choose… |
|---|---|
| Relies on the proxy to do normalization |
|
| Normalizes request paths based on RFC 3986 and does not merge slashes. |
|
| Normalizes request paths based on RFC 3986 and merges slashes, but does not decode percent-encoded slashes. |
|
| Normalizes request paths based on RFC 3986, decodes percent-encoded slashes, and merges slashes. |
|
| Processes request paths in a way that is incompatible with RFC 3986. |
|