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.

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

feat(context): custom context matcher #59

Merged
merged 1 commit into from
Mar 23, 2016
Merged

Conversation

chimurai
Copy link
Owner

Implements custom context matcher.

This allows you to provide a function to fully customise the filtering behaviour.
Besides the request path you'll get access to the request object for more contextual data to determine whether to proxy or not.

fixes: #58

@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 99.303% when pulling 9d8f839 on custom-context-matching into 483f757 on master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-39.4%) to 59.93% when pulling bd98185 on custom-context-matching into 483f757 on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.01%) to 99.303% when pulling 814e0fc on custom-context-matching into 483f757 on master.

@chimurai chimurai merged commit ea41a26 into master Mar 23, 2016
@chimurai chimurai deleted the custom-context-matching branch March 23, 2016 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How can I proxy only GET method
2 participants