mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-08 13:49:15 -05:00
Docker label rules[].value for path matchers is translated to capital letters #760
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#760
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Quantum1337 on GitHub (Nov 4, 2025).
Describe the Bug
Hello,
I´m using the blueprint feature together with docker labels. I´m encountering a problem with v1.12.1. The Labels are
translated to capital letters:
It seems that the rules are somehow case sensitive. It doesn´t work correctly for the capital lettters. When I´m changing it to lower case manually, everything works as expected.
Thank you for your work !
Environment
To Reproduce
Write a rule with lower case pathes
Expected Behavior
The path is exactly translated -> lower case
@radokristof commented on GitHub (Nov 5, 2025):
I have the same issue. It seemed correct before upgrading to 1.12.1 (from 1.11.x)
@tullisar commented on GitHub (Nov 5, 2025):
Yeah this breaks the path matching rules defined in the blueprint. I can workaround it temporarily by changing the rules in the Pangolin UI, but as soon as I restart the affected service the paths revert to all caps.
@Quantum1337 commented on GitHub (Nov 5, 2025):
Depending how the priority of your rules is, this might be a also a security issue, without noticing:
=> "Some/path" is now exposed, as it translates to "SOME/PATH" and so it does not match anymore.
@tullisar commented on GitHub (Nov 5, 2025):
It also seems to revert on its own after a bit (presumably there's a mechanism for refreshing the blueprint even without a container restart).
@tullisar commented on GitHub (Nov 6, 2025):
This commit:
5940bbd498Seems to be the culprit? The commit message "Uppercase" is pretty vague as to the reason for this change.
@oschwartz10612 commented on GitHub (Nov 8, 2025):
This will be fixed in the next patch. The issue was I was trying to fix people entering in lower case country codes but forgot about the other match types 😅. It should not only uppercase it if it is a country match type.