-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add 2 properties to OcelotPipelineConfiguration
class for more flexibility in pipeline
#1497
base: develop
Are you sure you want to change the base?
Conversation
…into develop Cherry picked from ThreeMammals#1497
5effa06
to
3560bb9
Compare
The feature branch has been rebased onto ThreeMammals:develop! @ArsalanMoniee |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you correct you PR title :
claas => class
pipieeline => pipeline
OcelotPipelineConfiguration
class for more flexibility in pipeline
2a8f3dc
to
2c7ded4
Compare
2c7ded4
to
4873224
Compare
The branch has been rebased onto release/24.0 with top commit 59b63ea ! |
4873224
to
9bee3af
Compare
9bee3af
to
0b704a9
Compare
…operty to OcelotPipelineConfiguration claas for more flexibility in pipieline
… characters: should_*
…l prevent derived types that introduce a finalizer from needing to re-implement 'IDisposable' to call it.
0b704a9
to
f8662f4
Compare
Fixes / New Feature
In a recent project, I needed to use existing and custom Authorization side by side. In the current situation, using custom Authorization before the original Authorization would reduce performance. Because in my custom Authorization service, it was necessary to call a specific web API.
Calling that web API before authentication would create a load for routes which were not existed in upstream. (ocelot json)
as well as the web API only call for valid request!
Proposed Changes
OcelotPipelineConfiguration
class for more flexibility in Ocelot's pipeline