fix: normalize hosts and SNIs so uppercase hostnames stay routable by AlinsRan · Pull Request #455 · api7/api7-ingress-controller

AlinsRan · 2026-08-06T06:54:44Z

Type of change:

Bugfix

What this PR does / why we need it:

Sync of apache/apisix-ingress-controller#2837.

An ApisixRoute whose match.hosts contains an uppercase character is silently unroutable: every request for that host returns 404, on every path and for every casing of the request Host header.

Route matching runs against $host, which nginx always lowercases (ngx_http_validate_host()). APISIX normalizes the route object to match, in apisix/router.lua:

if route.value.host then
    route.value.host = str_lower(route.value.host)
elseif route.value.hosts then
    for i, v in ipairs(route.value.hosts) do
        route.value.hosts[i] = str_lower(v)
    end
end

apisix/http/service.lua has no equivalent, so service.hosts is stored verbatim, and the default radixtree_host_uri router keys its host buckets on the raw reversed host string:

for i, host in ipairs(hosts) do
    local host_rev = host:reverse()

An uppercase host therefore ends up in a bucket keyed on e.g. moc.elpmaxe.esaCdexiM, which the lowercase $host can never reach. The controller carries the host constraint on the service object only, so nothing normalizes it on the way in either.

How

internal/ssl.NormalizeHosts already lowercases, trims and deduplicates hosts, and both the webhook conflict detector and the SSL indexer use it. The translator did not — so what the controller matched on and what it wrote to the data plane could disagree. This routes the four service.Hosts sites and the three ssl.Snis sites through it.

Two more defects fall out of the same gap:

dedupGatewaySSLSNIs compares SNIs verbatim, so two listeners claiming the same SNI in different cases were never recognised as colliding and both reached the data plane, which rejects duplicate SNIs.
TranslateGRPCRoute appends the listener hostnames to the route hostnames, which repeat in the common case, while the APISIX service schema declares uniqueItems on hosts. Covered by a new unit test that produces ["example.com", "example.com"] without the fix.

Only ApisixRoute and ApisixTls can carry an uppercase host today — Ingress hosts are validated as DNS-1123 subdomains and the Gateway API Hostname type has a lowercase-only pattern — but the hostnames extracted from a certificate's SAN are unconstrained too.

Verification

Reproduced end to end on apache/apisix:3.16.0-debian in standalone mode, with service.hosts: ["MixedCase.example.com"] and a route carrying no hosts of its own:

request `Host`	`radixtree_host_uri` (default)	`radixtree_uri`
`MixedCase.example.com`	404	200
`mixedcase.example.com`	404	200
`lowercase.example.com` (control)	200	200

radixtree_uri is unaffected because lua-resty-radixtree lowercases hosts itself, on both the config and the request side.

The data plane asymmetry is fixed separately in apache/apisix#13781 and api7/api7-ee-3-gateway#2084; this change also keeps existing data plane versions working.

Pre-submission checklist:

Did you explain what problem does this PR solve? Or what new features have been added?
Have you added corresponding test cases?
Have you modified the corresponding document?
Is this PR backward compatible?

Summary by CodeRabbit

Bug Fixes
- Hostnames are now normalized consistently across HTTP, gRPC, ingress, TLS, and gateway routing.
- Duplicate hostnames are removed after normalization, improving routing and TLS consistency.
- Requests using uppercase or lowercase host headers now resolve reliably to the same route.
Tests
- Added coverage for hostname normalization, duplicate removal, nil host handling, and mixed-case host requests.

An ApisixRoute whose `match.hosts` contains an uppercase character is silently unroutable: every request for that host returns 404, on every path and for every casing of the request `Host` header. Route matching runs against `$host`, which nginx always lowercases. APISIX normalizes the route object to match, in `apisix/router.lua`, but `apisix/http/service.lua` has no equivalent, so `service.hosts` is stored verbatim while the default `radixtree_host_uri` router keys its host buckets on the raw reversed host string. An uppercase host therefore lands in a bucket the lowercase `$host` can never reach. The controller carries the host constraint on the service object only, so nothing normalizes it. `internal/ssl.NormalizeHosts` already lowercases, trims and deduplicates, and both the webhook conflict detector and the SSL indexer use it. The translator did not, so what the controller matched on and what it wrote to the data plane could disagree. Route the four `service.Hosts` sites and the three `ssl.Snis` sites through it. Two more defects fall out of the same gap: - `dedupGatewaySSLSNIs` compares SNIs verbatim, so two listeners claiming the same SNI in different cases were never recognised as colliding and both reached the data plane, which rejects duplicate SNIs. - GRPCRoute appends the listener hostnames to the route hostnames, which repeat in the common case, while the APISIX service schema declares `uniqueItems` on hosts. Only ApisixRoute and ApisixTls can carry an uppercase host today — Ingress hosts are validated as DNS-1123 subdomains and Gateway API `Hostname` has a lowercase-only pattern — but the hostnames extracted from a certificate's SAN are unconstrained too. Sync of apache/apisix-ingress-controller#2837. The data plane side is fixed in apache/apisix#13781 and api7/api7-ee-3-gateway#2084.

coderabbitai · 2026-08-06T06:55:02Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f8c21609-2a4a-4809-b277-69d84f396af3

📥 Commits

Reviewing files that changed from the base of the PR and between bdd6fb4 and 110dc8d.

📒 Files selected for processing (9)

internal/adc/translator/apisixroute.go
internal/adc/translator/apisixroute_test.go
internal/adc/translator/apisixtls.go
internal/adc/translator/gateway.go
internal/adc/translator/grpcroute.go
internal/adc/translator/grpcroute_test.go
internal/adc/translator/httproute.go
internal/adc/translator/ingress.go
test/e2e/crds/v2/route.go

📝 Walkthrough

Walkthrough

The translators now normalize hostnames before generating APISIX services, routes, and SSL objects. Tests cover lowercasing, duplicate removal, wildcard preservation, nil hosts, and case-insensitive HTTP requests.

Changes

Hostname normalization

Layer / File(s)	Summary
Route hostname normalization `internal/adc/translator/apisixroute.go`, `internal/adc/translator/grpcroute.go`, `internal/adc/translator/httproute.go`, `internal/adc/translator/ingress.go`	HTTP, gRPC, Ingress, and APISIX route hostnames are normalized before service assignment and priority calculation.
TLS hostname normalization `internal/adc/translator/apisixtls.go`, `internal/adc/translator/gateway.go`, `internal/adc/translator/ingress.go`	TLS hostnames and Gateway SNIs are normalized before SSL generation and deduplication.
Normalization validation `internal/adc/translator/apisixroute_test.go`, `internal/adc/translator/grpcroute_test.go`, `test/e2e/crds/v2/route.go`	Tests verify lowercasing, duplicate removal, wildcard preservation, nil hosts, and requests with different `Host` casing.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

api7/api7-ingress-controller#392: Both changes modify APISIX route and service hostname handling.

Suggested reviewers: nic-6443, shreemaan-abhishek

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
E2e Test Quality Review	⚠️ Warning	The E2E test covers only ApisixRoute; no test exercises the new ApisixTls or Gateway SNI normalization and case-insensitive collision behavior.	Add an E2E TLS scenario for mixed-case SNI and a Gateway listener collision case; assert normalized data-plane SSL objects and successful HTTPS routing.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: normalizing hosts and SNIs to keep uppercase hostnames routable.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Security Check	✅ Passed	The diff only normalizes host and SNI strings and adds tests. It adds no secret logging or storage, authorization or ownership logic, insecure TLS flags, shared-resource access, or secret-reference...

✨ Finishing Touches

📝 Generate docstrings

Create stacked PR
Commit on current branch

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch fix/normalize-hosts-lowercase

_{Comment @coderabbitai help to get the list of available commands.}

github-actions · 2026-08-06T07:06:21Z

conformance test report - apisix-standalone mode

apiVersion: gateway.networking.k8s.io/v1
date: "2026-08-06T07:03:17Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.6.0
implementation:
  contact:
  - https://github.com/apache/apisix-ingress-controller/issues
  organization: APISIX
  project: apisix-ingress-controller
  url: https://github.com/apache/apisix-ingress-controller.git
  version: v2.0.0
kind: ConformanceReport
mode: default
profiles:
- core:
    result: partial
    skippedTests:
    - HTTPRouteHTTPSListener
    - HTTPRouteInvalidBackendRefUnknownKind
    - HTTPRouteInvalidCrossNamespaceBackendRef
    - HTTPRouteInvalidNonExistentBackendRef
    - HTTPRouteListenerHostnameMatching
    - HTTPRouteMultipleGateways
    - HTTPRouteNoBackendRefs
    statistics:
      Failed: 0
      Passed: 30
      Skipped: 7
  extended:
    result: partial
    skippedTests:
    - HTTPRouteRedirectPortAndScheme
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRoute303RedirectStatusCode
    - HTTPRoute307RedirectStatusCode
    - HTTPRoute308RedirectStatusCode
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteRetry
    - HTTPRouteRetryBackendTimeout
    - HTTPRouteRetryConnectionError
    - ListenerSet
  name: GATEWAY-HTTP
  summary: Core tests partially succeeded with 7 test skips. Extended tests partially
    succeeded with 1 test skips.
- core:
    result: partial
    skippedTests:
    - GRPCRouteListenerHostnameMatching
    statistics:
      Failed: 0
      Passed: 14
      Skipped: 1
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
  name: GATEWAY-GRPC
  summary: Core tests partially succeeded with 1 test skips. Extended tests succeeded.
- core:
    result: partial
    skippedTests:
    - TLSRouteHostnameIntersection
    - TLSRouteInvalidBackendRefNonexistent
    - TLSRouteInvalidBackendRefUnknownKind
    - TLSRouteSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 16
      Skipped: 4
  extended:
    result: partial
    skippedTests:
    - TLSRouteTerminateSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 3
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - TLSRouteModeTerminate
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
    - TLSRouteModeMixed
  name: GATEWAY-TLS
  summary: Core tests partially succeeded with 4 test skips. Extended tests partially
    succeeded with 1 test skips.
succeededProvisionalTests:
- GatewayOptionalAddressValue

github-actions · 2026-08-06T07:06:26Z

conformance test report - apisix mode

apiVersion: gateway.networking.k8s.io/v1
date: "2026-08-06T07:03:21Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.6.0
implementation:
  contact:
  - https://github.com/apache/apisix-ingress-controller/issues
  organization: APISIX
  project: apisix-ingress-controller
  url: https://github.com/apache/apisix-ingress-controller.git
  version: v2.0.0
kind: ConformanceReport
mode: default
profiles:
- core:
    result: partial
    skippedTests:
    - HTTPRouteHTTPSListener
    - HTTPRouteInvalidBackendRefUnknownKind
    - HTTPRouteInvalidCrossNamespaceBackendRef
    - HTTPRouteInvalidNonExistentBackendRef
    - HTTPRouteListenerHostnameMatching
    - HTTPRouteMultipleGateways
    - HTTPRouteNoBackendRefs
    statistics:
      Failed: 0
      Passed: 30
      Skipped: 7
  extended:
    result: partial
    skippedTests:
    - HTTPRouteRedirectPortAndScheme
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRoute303RedirectStatusCode
    - HTTPRoute307RedirectStatusCode
    - HTTPRoute308RedirectStatusCode
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteRetry
    - HTTPRouteRetryBackendTimeout
    - HTTPRouteRetryConnectionError
    - ListenerSet
  name: GATEWAY-HTTP
  summary: Core tests partially succeeded with 7 test skips. Extended tests partially
    succeeded with 1 test skips.
- core:
    result: partial
    skippedTests:
    - GRPCRouteListenerHostnameMatching
    statistics:
      Failed: 0
      Passed: 14
      Skipped: 1
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
  name: GATEWAY-GRPC
  summary: Core tests partially succeeded with 1 test skips. Extended tests succeeded.
- core:
    result: partial
    skippedTests:
    - TLSRouteHostnameIntersection
    - TLSRouteInvalidBackendRefNonexistent
    - TLSRouteInvalidBackendRefUnknownKind
    - TLSRouteSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 16
      Skipped: 4
  extended:
    result: partial
    skippedTests:
    - TLSRouteTerminateSimpleSameNamespace
    statistics:
      Failed: 0
      Passed: 3
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - TLSRouteModeTerminate
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
    - TLSRouteModeMixed
  name: GATEWAY-TLS
  summary: Core tests partially succeeded with 4 test skips. Extended tests partially
    succeeded with 1 test skips.
succeededProvisionalTests:
- GatewayOptionalAddressValue

github-actions · 2026-08-06T07:25:49Z

conformance test report

apiVersion: gateway.networking.k8s.io/v1
date: "2026-08-06T07:22:45Z"
gatewayAPIChannel: experimental
gatewayAPIVersion: v1.6.0
implementation:
  contact:
  - https://github.com/apache/apisix-ingress-controller/issues
  organization: APISIX
  project: apisix-ingress-controller
  url: https://github.com/apache/apisix-ingress-controller.git
  version: v2.0.0
kind: ConformanceReport
mode: default
profiles:
- core:
    failedTests:
    - GatewayModifyListeners
    - HTTPRouteExactPathMatching
    - HTTPRouteMultipleGateways
    - HTTPRouteNoBackendRefs
    result: failure
    skippedTests:
    - HTTPRouteHTTPSListener
    statistics:
      Failed: 4
      Passed: 32
      Skipped: 1
  extended:
    result: partial
    skippedTests:
    - HTTPRouteRedirectPortAndScheme
    statistics:
      Failed: 0
      Passed: 12
      Skipped: 1
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - HTTPRouteBackendProtocolWebSocket
    - HTTPRouteDestinationPortMatching
    - HTTPRouteHostRewrite
    - HTTPRouteMethodMatching
    - HTTPRoutePathRewrite
    - HTTPRoutePortRedirect
    - HTTPRouteQueryParamMatching
    - HTTPRouteRequestMirror
    - HTTPRouteResponseHeaderModification
    - HTTPRouteSchemeRedirect
    unsupportedFeatures:
    - BackendTLSPolicy
    - BackendTLSPolicySANValidation
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - HTTPRoute303RedirectStatusCode
    - HTTPRoute307RedirectStatusCode
    - HTTPRoute308RedirectStatusCode
    - HTTPRouteBackendProtocolH2C
    - HTTPRouteBackendRequestHeaderModification
    - HTTPRouteBackendTimeout
    - HTTPRouteCORS
    - HTTPRouteNamedRouteRule
    - HTTPRouteParentRefPort
    - HTTPRoutePathRedirect
    - HTTPRouteRequestMultipleMirrors
    - HTTPRouteRequestPercentageMirror
    - HTTPRouteRequestTimeout
    - HTTPRouteRetry
    - HTTPRouteRetryBackendTimeout
    - HTTPRouteRetryConnectionError
    - ListenerSet
  name: GATEWAY-HTTP
  summary: Core tests failed with 4 test failures. Extended tests partially succeeded
    with 1 test skips.
- core:
    failedTests:
    - GatewayModifyListeners
    result: failure
    statistics:
      Failed: 1
      Passed: 14
      Skipped: 0
  extended:
    result: success
    statistics:
      Failed: 0
      Passed: 1
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
  name: GATEWAY-GRPC
  summary: Core tests failed with 1 test failures. Extended tests succeeded.
- core:
    failedTests:
    - GatewayModifyListeners
    - TLSRouteHostnameIntersection
    - TLSRouteInvalidBackendRefNonexistent
    - TLSRouteInvalidBackendRefUnknownKind
    - TLSRouteSimpleSameNamespace
    result: failure
    statistics:
      Failed: 5
      Passed: 15
      Skipped: 0
  extended:
    failedTests:
    - TLSRouteTerminateSimpleSameNamespace
    result: failure
    statistics:
      Failed: 1
      Passed: 3
      Skipped: 0
    supportedFeatures:
    - GatewayAddressEmpty
    - GatewayPort8080
    - TLSRouteModeTerminate
    unsupportedFeatures:
    - GatewayBackendClientCertificate
    - GatewayFrontendClientCertificateValidation
    - GatewayFrontendClientCertificateValidationInsecureFallback
    - GatewayHTTPListenerIsolation
    - GatewayHTTPSListenerDetectMisdirectedRequests
    - GatewayInfrastructurePropagation
    - GatewayStaticAddresses
    - ListenerSet
    - TLSRouteModeMixed
  name: GATEWAY-TLS
  summary: Core tests failed with 5 test failures. Extended tests failed with 1 test
    failures.
succeededProvisionalTests:
- GatewayOptionalAddressValue

AlinsRan self-assigned this Aug 7, 2026

jarvis9443 approved these changes Aug 7, 2026

View reviewed changes

AlinsRan merged commit 079d58a into master Aug 7, 2026
32 of 35 checks passed

AlinsRan deleted the fix/normalize-hosts-lowercase branch August 7, 2026 03:56

Navigation Menu

Uh oh!

fix: normalize hosts and SNIs so uppercase hostnames stay routable - #455

fix: normalize hosts and SNIs so uppercase hostnames stay routable#455
AlinsRan merged 1 commit into
masterfrom
fix/normalize-hosts-lowercase

AlinsRan commented Aug 6, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Aug 6, 2026 •

edited

Loading

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

github-actions Bot commented Aug 6, 2026

Uh oh!

github-actions Bot commented Aug 6, 2026

Uh oh!

github-actions Bot commented Aug 6, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

AlinsRan commented Aug 6, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Type of change:

What this PR does / why we need it:

How

Verification

Pre-submission checklist:

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

github-actions Bot commented Aug 6, 2026

conformance test report - apisix-standalone mode

Uh oh!

github-actions Bot commented Aug 6, 2026

conformance test report - apisix mode

Uh oh!

github-actions Bot commented Aug 6, 2026

conformance test report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

AlinsRan commented Aug 6, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 6, 2026 •

edited

Loading