Improve Ignore Path Matching to Avoid False Positives

[georgidhristov]

Description

DebugProbe currently uses StartsWith when evaluating ignored paths.

This can cause unrelated endpoints to be ignored when their route begins with an ignored path value.

Current Behavior

If the following path is configured:

builder.Services.AddDebugProbe(options =>
{
    options.IgnorePaths =
    [
        "/health"
    ];
});

The following requests are ignored:

/health
/health/
/health/status

But these are also ignored:

/healthcare
/health-checks
/healthy

even though they are unrelated endpoints.

Expected Behavior

Ignore path matching should only match:

• exact path matches
• valid child paths beneath the configured path

For example, configuring:

/health

should ignore:

/health
/health/
/health/status

but should not ignore:

/healthcare
/health-checks
/healthy

Suggested Fix

Replace the current StartsWith matching with boundary-aware path matching.

Recommended logic:

• Match when the request path equals the ignored path.
• Match when the request path starts with the ignored path followed by /.
• Do not match partial route prefixes.

Result

After this change:

• Ignore path behavior becomes more predictable.
• Unrelated endpoints are no longer excluded accidentally.
• Health, readiness, and liveness endpoints continue to work as expected.
• Route matching aligns more closely with developer expectations.

[viogustian]

Hi @georgidhristov! I'm looking for a good first issue to start contributing to C# open-source, and I would love to take this on. Could you please assign this to me?

[georgidhristov]

Thanks for your interest and welcome to the project. I've assigned the issue to you. If you have any questions while working on it, feel free to ask. Good luck with your first open-source contribution.