Case-insensitive path matching support added for ingress path

[mustafasemihbay]

Normally, haproxy-kubernetes-ingress performs path matching in a case-sensitive manner. However, ingress-nginx supports case-insensitive path matching. During migrations from ingress-nginx to haproxy-kubernetes-ingress, some projects may require case-insensitive path matching behavior.

This change introduces an optional feature that enables case-insensitive path matching.

The feature can be enabled by passing an extra argument in the Helm chart configuration:

extraArgs:

• --case-insensitive-path-match

kubernetes ingress example;

spec:
ingressClassName: haproxy
rules:
- host: example.com
http:
paths:
- path: /example-api
pathType: ImplementationSpecific
backend:
service:
name: example-api
port:
number: 80

this ingress path match with example.com/example-api, example.com/Example-api, example.com/EXAMPLE-api etc.

[ivanmatmati]

Hi @mustafasemihbay , thanks for your submission. Can you make the required changes as reported by the above checks ? Have a great day.

[ivanmatmati]

Hi @mustafasemihbay , can you check your expected behavior with case insensitivity matching in this setting:

spec:
ingressClassName: haproxy
rules:
- host: example.com
http:
paths:
- path: /Example-api
pathType: ImplementationSpecific
backend:
service:
name: example-api
port:
number: 80

Notice the capital letter for the path and then try to match it.

[maharshi9c]

Is there any update on this issue

Description

HAProxy Kubernetes Ingress Controller (v3.2.5, Helm chart 1.48.0) performs case-sensitive path matching with no working workaround available in the current release.

The problem

Ingress paths stored in path-prefix.map and path-exact.map are matched case-sensitively against incoming request paths. When a client sends a path that differs only in case from the defined ingress path, HAProxy returns HTTP 404 even though the path logically matches.

Example:

• Ingress defines: /api/ForgotUsernamePassword/validate-credentials
• Client sends: /api/forgotUsernamePassword/validate-credentials
• Result: HTTP 404 — no match in the map

This broke a production service after migration from Nginx (which matches paths case-insensitively by default).

---

Expected Behaviour

One of the following should work but its not working - getting same 404 issue

1. Inline (?i) regex flag in the ingress path should enable case-insensitive matching for that path, e.g.:

   paths:
     - path: /(?i)api/ForgotUsernamePassword/.*
       pathType: ImplementationSpecific
   

[maharshi9c]

Steps to Reproduce

1. Create an ingress with haproxy.org/use-regex: "true" and a path using (?i)

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: test-case-insensitive
namespace: hqy-applications
annotations:
haproxy.org/ingress.class: "haproxy"
haproxy.org/use-regex: "true"
haproxy.org/path-match: "regex"
spec:
ingressClassName: haproxy
rules:
- host: api.example.com
http:
paths:
- path: /(?i)api/MyService/.*
pathType: ImplementationSpecific
backend:
service:
name: my-service
port:
number: 80

Note on Kubernetes validation: The path (?i)/api/... (flag before the /) is rejected by Kubernetes with: "must be an absolute path". The only form that passes validation is /(?i)api/... (flag after the leading /), which is what we used.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[dkorunic]

Let's not keep this stale, we also have a PR on Helm Chart side as well.