Please document the ProxyMatch "Path" pattern syntax

[aschuhardt]

What should we add or change to make your life better?

Provide documentation for how to write ProxyMatch path patterns.

Why is this important to you?

The examples provided only illustrate that the string /{**catch-all} works, somehow, and doesn't go into any detail about the syntax used. I have no idea how to use this.

Questions:

• Does the word "catch-all" have special meaning?
• What does ** mean? Is it different from a single *?
• How do I specify more complex patterns?
• Can we specify exclusions? i.e. /{^error} or something to exclude paths that start with the word "error"

[Tratcher]

The path pattern is passed through to the AspNetCore routing system which is documented here:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-5.0#route-template-reference

We should make sure our docs have the appropriate references back to the AspNetCore docs.

[aschuhardt]

The path pattern is passed through to the AspNetCore routing system which is documented here:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-5.0#route-template-reference

We should make sure our docs have the appropriate references back to the AspNetCore docs.

Thank you for that info. Yes having that link someplace in the YARP docs would be very helpful.

[karelz]

Triage: We should provide link from our docs.

[jeremyb35]

Did you find a way to specify an exclusion ?
I'm looking for the exact same thing, but I cannot find any way to do it after many hours of research...

I've also tried to put regex, but it did not work at all :(

[aschuhardt]

Did you find a way to specify an exclusion ? I'm looking for the exact same thing, but I cannot find any way to do it after many hours of research...

I've also tried to put regex, but it did not work at all :(

I didn't.