Route OPTIONS Resource Traffic to the Backend #12723
Merged
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.
Description
Resources having the OPTIONS method bring to the 0th index of the
acceptableResourcesList
to be selected in thedispatcher.findResource
logic when routing the OPTIONS traffic to backend.Bump the Synapse version to
4.0.0-wso2v152
Set the current API object to the
MessageContext
from theDefaultAPIHandler
Related Issue: OPTIONS Resource Request doesn't goes to the backend (returning all x-jwt-Assertion back to the client) api-manager#2226
Resolves NPE in the AnalyticsMetricsHandler when invoking unavailable method api-manager#3377