Skip to content

Latest commit

 

History

History

airlock-microgateway

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

Airlock Microgateway

Table of contents

API channel Implementation version Mode Report
standard v4.5.0 default link

Reproduce

The Airlock Microgateway conformance report can be reproduced by following the steps in the Gateway API conformance guide on GitHub.

Note

The HTTPRouteWeight test fires 10 concurrent request to 3 backends totaling in 500 requests to assert a distribution that matches the configured weight. Please be aware that this test exceeds the 5 req/sec rate-limit enforced in the community edition , causing the test to fail. To successfully pass this test a premium license is required.

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. Therefore, to run the conformance tests, a ContentSecurityPolicy with a HeaderRewrites (see conformance-report.yaml) is required to disable request header filtering for all HTTPRoute tests relying on the MakeRequestAndExpectEventuallyConsistentResponse assertion. 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.