[GH-ISSUE #1197] [Suggestion] UUID wildcard #1190

New issue

Open

opened 2026-03-03 19:49:10 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 19:49:10 +03:00

Owner

Originally created by @crankygeek on GitHub (Apr 6, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1197

Originally assigned to: @NghiaTranUIT on GitHub.

I had a thought that it would be handy if Proxyman had a pre-configured token/wildcard (or whatever) to represent UUIDs. So instead of an ungainly looking URL such as:

https://example.com/users/[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}/transfers/accounts

You could instead have:

https://example.com/users/uuid-token/transfers/accounts

There's probably lots of problems with this suggestion that I'm not thinking of, but after running through several breakpoints this morning, it sounded like something worth suggesting. :)

Originally created by @crankygeek on GitHub (Apr 6, 2022). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1197 Originally assigned to: @NghiaTranUIT on GitHub. I had a thought that it would be handy if Proxyman had a pre-configured token/wildcard (or whatever) to represent UUIDs. So instead of an ungainly looking URL such as: https://example.com/users/[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}/transfers/accounts You could instead have: https://example.com/users/uuid-token/transfers/accounts There's probably lots of problems with this suggestion that I'm not thinking of, but after running through several breakpoints this morning, it sounded like something worth suggesting. :)

kerem added the

enhancement

label

2026-03-03 19:49:10 +03:00

kerem commented

2026-03-03 19:49:11 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Apr 7, 2022):

Thanks for your suggestion. Behind the scene, the Wildcard will be transformed into an actual Regex Expression.

Thus, your "not beautiful" URL (https://example.com/users/[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}/transfers/accounts) would work fine.

I don't think adding https://example.com/users/uuid-token/transfers/accounts would be better since it breaks the current logic.

I suppose that I can have a list of common wildcard/regex pattern that allows you to copy, would be better 😄

@NghiaTranUIT commented on GitHub (Apr 7, 2022): Thanks for your suggestion. Behind the scene, the Wildcard will be transformed into an actual Regex Expression. Thus, your "not beautiful" URL ([https://example.com/users/[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}/transfers/accounts](https://example.com/users/%5B0-9a-fA-F%5D%7B8%7D-%5B0-9a-fA-F%5D%7B4%7D-%5B0-9a-fA-F%5D%7B4%7D-%5B0-9a-fA-F%5D%7B4%7D-%5B0-9a-fA-F%5D%7B12%7D/transfers/accounts)) would work fine. I don't think adding `https://example.com/users/uuid-token/transfers/accounts` would be better since it breaks the current logic. I suppose that I can have a list of common wildcard/regex pattern that allows you to copy, would be better 😄

kerem commented

2026-03-03 19:49:11 +03:00

Author

Owner

@crankygeek commented on GitHub (Apr 7, 2022):

I'm not sure I explained this very well, sorry! I didn't meant to suggest any changes to how UUIDs are handled, just how they're represented in the Proxyman UI. For example, here's a sample from the Breakpoints rules screens with wildcards, my proposed "tokens", and actual regex. It gets difficult to read if there are multiple UUIDs in the URL, especially if they exceed the visible width of the field and/or dialog.

The Scripting editor has similar issues. I do think any tokens would definitely need to be visually distinct from text. I was thinking of maybe something like the capsule style of the "Block List" or "Proxy overridden" indicators in Proxyman's status bar at the bottom. I recognize that doing something like this would certainly add complexity to these fields.

This is certainly not something I would prioritize. I was mainly hoping the suggestion would give you something to think about. I do like the idea of providing common regex patterns. While it wouldn't improve the UI, reducing the potential for typos in user-entered regex patterns would certainly be appreciated. :) Do you have any sense of what other types of patterns are common?

@crankygeek commented on GitHub (Apr 7, 2022): I'm not sure I explained this very well, sorry! I didn't meant to suggest any changes to how UUIDs are handled, just how they're represented in the Proxyman UI. For example, here's a sample from the Breakpoints rules screens with wildcards, my proposed "tokens", and actual regex. It gets difficult to read if there are multiple UUIDs in the URL, especially if they exceed the visible width of the field and/or dialog. ![breakpoints](https://user-images.githubusercontent.com/1638278/162257733-261b30db-b6eb-4f0d-898d-f5644a633e70.png) The Scripting editor has similar issues. I do think any tokens would definitely need to be visually distinct from text. I was thinking of maybe something like the capsule style of the "Block List" or "Proxy overridden" indicators in Proxyman's status bar at the bottom. I recognize that doing something like this would certainly add complexity to these fields. This is certainly not something I would prioritize. I was mainly hoping the suggestion would give you something to think about. I do like the idea of providing common regex patterns. While it wouldn't improve the UI, reducing the potential for typos in user-entered regex patterns would certainly be appreciated. :) Do you have any sense of what other types of patterns are common?