Case *sensitive* path matching

[u8sand]

What do you want to happen?

It would be nice to have an option to enable case sensitive path matching as opposed to case insensitive path matching, perhaps globally. In-fact, the current kubernetes spec (and indeed since v1.18) seems to suggest "Prefix" path type would be case sensitive.

From: https://kubernetes.io/docs/concepts/services-networking/ingress/#path-types

• Exact: Matches the URL path exactly and with case sensitivity.
• Prefix: Matches based on a URL path prefix split by /. Matching is case sensitive and done on a path element by element basis. A path element refers to the list of labels in the path split by the / separator. A request is a match for path p if every p is an element-wise prefix of p of the request path.

Very explicitly:

An ingress with the path: /MyWebsite should not match the url /mywebsite.

What's the use-case for this you might ask? We have a catch-all provider which corrects misspellings (which would include casing issues); but it can't work if /MyWebsite gets sent to /mywebsite. Some case sensitive backends like tomcat will show a 404 instead of the site at /mywebsite.

Is there currently another issue associated with this?

No issue found.

Does it require a particular kubernetes version?

I don't believe it should require a particular version, though if the goal is to match the spec I guess it'd be v1.18+

If this is actually about documentation, add /kind documentation below

If there is a way to do this, or i'm just mistaken; it would be helpful to document it explicitly. A search for case, sensitivity, or strict on the docs turns up nothing.

/kind feature

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[u8sand]

For anyone who needs this, I made the following patch:

--- nginx.tmpl.orig	2020-05-12 13:18:43.000000000 -0400
+++ nginx.tmpl	2021-09-21 16:18:40.346643696 -0400
@@ -1015,7 +1015,12 @@
         }
         {{ end }}
 
+        # replace case insensitive with case sensitive
+        {{ if hasPrefix $path "~*" }}
+        location ~ {{ slice $path 2 }} {
+        {{ else }}
         location {{ $path }} {
+        {{ end }}
             {{ $ing := (getIngressInformation $location.Ingress $server.Hostname $location.Path) }}
             set $namespace      {{ $ing.Namespace | quote}};
             set $ingress_name   {{ $ing.Rule | quote }};

You can produce a new nginx.tmpl by applying the patch and mount it into the docker container over the existing file.

Clearly it's possible to add this as an option, but I have no clue how to build this container so this was easiest for me.