Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Looks like there isn't a way to configure the whitelist for the gleak.middleware instance created internally? #8

Open
shzmilydahlke opened this issue Jul 14, 2016 · 1 comment
Open

Looks like there isn't a way to configure the whitelist for the gleak.middleware instance created internally? #8

shzmilydahlke opened this issue Jul 14, 2016 · 1 comment

Comments

@shzmilydahlke
Copy link

I want to use the express api middleware to have gleak run on every http request, but doesn't look like this use is designed to allow whitelisting (as the Gleak instance is internal to the method and inaccessible).
Is there a way to open up this path to be whitelist configurable?
@aheckmann
Copy link
Owner

yeah sounds good. we could refactor the middleware method to accept an options object and add a new property for the whitelist option or similar. PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aheckmann @shzmilydahlke