Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Disabling MiniProfiler header for specific endpoints
See original GitHub issueThis might be a weird scenario - I use MiniProfiler in my application for the user part and a separate API part. I’m completely happy with how the user portion is working however the API portion, while I am tracking the profiling information I want on the server, it is sending through the headers for client side performance tracking.
Is there a way to disable the X-MiniProfiler-Ids header for a specific path?
I tried options.IgnoredPaths.Add("/api/"); however that disabled profiling entirely. I know there is the MaxUnviewedProfiles setting and I could tweak that lower to avoid as many headers being sent though that seems more like a last-ditch effort rather than a solution.
If this doesn’t sound too weird and the functionality doesn’t exist, I’m happy to propose a PR adding something like this - probably similar to how the ShouldProfile option works by passing a Func<HttpRequest, bool>.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Turnerj I’m confused by this request still, is your config not working as intended and not rendering the headers? (even in non-dev? given that’s always true). Anything not authorized should not render the headers: https://github.com/MiniProfiler/dotnet/blob/main/src/MiniProfiler.AspNetCore/MiniProfilerMiddleware.cs#L191
No worries at all just thought I was crazy 😃 Glad you got it sorted! If that doesn’t do what you need in the end, please shout.