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
| standard |[v4.5.0](https://github.com/airlock/microgateway/releases/tag/4.5.0)| default |[v4.5.0 report](./standard-4.5.0-default-report.yaml)|
9
+
8
10
9
11
## Reproduce
10
12
@@ -14,3 +16,7 @@ The Airlock Microgateway conformance report can be reproduced by following the s
14
16
> The `HTTPRouteWeight` test fires 10 concurrent request to 3 backends totaling in 500 requests to assert a distribution that matches the configured weight.
15
17
> Please be aware that this test exceeds the [5 req/sec rate-limit](https://docs.airlock.com/microgateway/latest/#data/1675772882054.html) enforced in the <!-- markdown-link-check-disable -->[community edition](https://www.airlock.com/en/secure-access-hub/components/microgateway/community-edition)<!-- markdown-link-check-enable -->, causing the test to fail.
16
18
> To successfully pass this test a <!-- markdown-link-check-disable -->[premium license](https://www.airlock.com/en/secure-access-hub/components/microgateway/premium-edition)<!-- markdown-link-check-enable --> is required.
19
+
>
20
+
> The Airlock Microgateway drops all request headers except for a well-known built-in standard and tracing headers list (e.g., Accept, Cookie, X-CSRF-TOKEN) to reduce the attack surface.
21
+
> Therefore, to run the conformance tests, a `ContentSecurityPolicy` with a `HeaderRewrites` (see [`conformance-report.yaml`](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/manifests/conformance-report.yaml)) is required to disable request header filtering for all `HTTPRoute` tests relying on the `MakeRequestAndExpectEventuallyConsistentResponse` assertion.
22
+
> Regardless of whether request header filtering is enabled or disabled, header-based routing works as specified in the Gateway API, as the headers are only filtered before the request is forwarded to the upstream.
| standard |[v4.5.0](https://github.com/airlock/microgateway/releases/tag/4.5.0)| default |[link](./standard-4.5.0-default-report.yaml)|
8
+
9
+
## Reproduce
10
+
11
+
The Airlock Microgateway conformance report can be reproduced by following the steps in the [Gateway API conformance guide](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/conformance.md) on GitHub.
12
+
13
+
> [!NOTE]
14
+
> The `HTTPRouteWeight` test fires 10 concurrent request to 3 backends totaling in 500 requests to assert a distribution that matches the configured weight.
15
+
> Please be aware that this test exceeds the [5 req/sec rate-limit](https://docs.airlock.com/microgateway/latest/#data/1675772882054.html) enforced in the <!-- markdown-link-check-disable -->[community edition](https://www.airlock.com/en/secure-access-hub/components/microgateway/community-edition)<!-- markdown-link-check-enable -->, causing the test to fail.
16
+
> To successfully pass this test a <!-- markdown-link-check-disable -->[premium license](https://www.airlock.com/en/secure-access-hub/components/microgateway/premium-edition)<!-- markdown-link-check-enable --> is required.
17
+
>
18
+
> The Airlock Microgateway drops all request headers except for a well-known built-in standard and tracing headers list (e.g., Accept, Cookie, X-CSRF-TOKEN) to reduce the attack surface.
19
+
> Therefore, to run the conformance tests, a `ContentSecurityPolicy` with a `HeaderRewrites` (see [`conformance-report.yaml`](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/manifests/conformance-report.yaml)) is required to disable request header filtering for all `HTTPRoute` tests relying on the `MakeRequestAndExpectEventuallyConsistentResponse` assertion.
20
+
> Regardless of whether request header filtering is enabled or disabled, header-based routing works as specified in the Gateway API, as the headers are only filtered before the request is forwarded to the upstream.
| standard |[v4.5.0](https://github.com/airlock/microgateway/releases/tag/4.5.0)| default |[link](./standard-4.5.0-default-report.yaml)|
8
+
9
+
## Reproduce
10
+
11
+
The Airlock Microgateway conformance report can be reproduced by following the steps in the [Gateway API conformance guide](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/conformance.md) on GitHub.
12
+
13
+
> [!NOTE]
14
+
> The `HTTPRouteWeight` test fires 10 concurrent request to 3 backends totaling in 500 requests to assert a distribution that matches the configured weight.
15
+
> Please be aware that this test exceeds the [5 req/sec rate-limit](https://docs.airlock.com/microgateway/latest/#data/1675772882054.html) enforced in the <!-- markdown-link-check-disable -->[community edition](https://www.airlock.com/en/secure-access-hub/components/microgateway/community-edition)<!-- markdown-link-check-enable -->, causing the test to fail.
16
+
> To successfully pass this test a <!-- markdown-link-check-disable -->[premium license](https://www.airlock.com/en/secure-access-hub/components/microgateway/premium-edition)<!-- markdown-link-check-enable --> is required.
17
+
>
18
+
> The Airlock Microgateway drops all request headers except for a well-known built-in standard and tracing headers list (e.g., Accept, Cookie, X-CSRF-TOKEN) to reduce the attack surface.
19
+
> Therefore, to run the conformance tests, a `ContentSecurityPolicy` with a `HeaderRewrites` (see [`conformance-report.yaml`](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/manifests/conformance-report.yaml)) is required to disable request header filtering for all `HTTPRoute` tests relying on the `MakeRequestAndExpectEventuallyConsistentResponse` assertion.
20
+
> Regardless of whether request header filtering is enabled or disabled, header-based routing works as specified in the Gateway API, as the headers are only filtered before the request is forwarded to the upstream.
The Airlock Microgateway conformance report can be reproduced by following the steps in the [Gateway API conformance guide](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/conformance.md) on GitHub.
12
+
13
+
> [!NOTE]
14
+
> The `HTTPRouteWeight` test fires 10 concurrent request to 3 backends totaling in 500 requests to assert a distribution that matches the configured weight.
15
+
> Please be aware that this test exceeds the [5 req/sec rate-limit](https://docs.airlock.com/microgateway/latest/#data/1675772882054.html) enforced in the <!-- markdown-link-check-disable -->[community edition](https://www.airlock.com/en/secure-access-hub/components/microgateway/community-edition)<!-- markdown-link-check-enable -->, causing the test to fail.
16
+
> To successfully pass this test a <!-- markdown-link-check-disable -->[premium license](https://www.airlock.com/en/secure-access-hub/components/microgateway/premium-edition)<!-- markdown-link-check-enable --> is required.
17
+
>
18
+
> The Airlock Microgateway drops all request headers except for a well-known built-in standard and tracing headers list (e.g., Accept, Cookie, X-CSRF-TOKEN) to reduce the attack surface.
19
+
> Therefore, to run the conformance tests, a `ContentSecurityPolicy` with a `HeaderRewrites` (see [`conformance-report.yaml`](https://github.com/airlock/microgateway/tree/main/examples/gateway-api/conformance/manifests/conformance-report.yaml)) is required to disable request header filtering for all `HTTPRoute` tests relying on the `MakeRequestAndExpectEventuallyConsistentResponse` assertion.
20
+
> Regardless of whether request header filtering is enabled or disabled, header-based routing works as specified in the Gateway API, as the headers are only filtered before the request is forwarded to the upstream.
[Airlock Microgateway][airlock-microgateway] is a Kubernetes native WAAP (Web Application and API Protection) solution to protect microservices.
119
119
Modern application security is embedded in the development workflow and follows DevSecOps paradigms.
120
120
Airlock Microgateway protects your applications and microservices with the tried-and-tested Airlock security features against attacks, while also providing a high degree of scalability.
121
121
122
-
With [Airlock Microgateway 4.4][airlock-microgateway-v4.4], Airlock Microgateway introduces a sidecarless data plane mode
122
+
With [Airlock Microgateway 4.4][airlock-microgateway-gwapi-arch], Airlock Microgateway introduces a sidecarless data plane mode
123
123
based on Gateway API to avoid the operational complexity of sidecars.
124
124
125
125
#### Features
@@ -135,9 +135,9 @@ based on Gateway API to avoid the operational complexity of sidecars.
135
135
- Check our [Airlock community forum][airlock-microgateway-community-support] and [support process][airlock-microgateway-premium-support] for support.
0 commit comments