Add 2 properties to OcelotPipelineConfiguration
class for more flexibility in pipeline
#1497
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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