How can we avoid OPTION call in microgateway. or how do we fix this CORS in microgateway. The backend is capable of handling the CORS call. but the OPTION call is failing in apikey authentication itself in microgateway if apikey is passed in header, as OPTION call doesn't pass the header parameter. So I pass the apikey in query and it works fine, but the problem with this solution is the quota plugin for this proxy. every OPTION call is also consuming the quota which is wrong. so if I am having a 10 request per day quota. if I am hitting from a web application, I am only able to hit 5 API calls because of 5 OPTION call for each 5 POST calls. so I need to avoid the quota plugin also for OPTION call
Solved! Go to Solution.
You'll have to implement a custom plugin to handle this. Make sure the custom plugin appears BEFORE the oauth plugin in the config.yaml file.