Reference - https://stackoverflow.com/questions/29954037/why-is-an-options-request-sent-and-can-i-disable-it
\nOPTIONS requests are what we call pre-flight requests in Cross-origin resource sharing (CORS).
This pre-flight request is made by some browsers as a safety measure to ensure that the request being done is trusted by the server. Meaning the server understands that the method, origin and headers being sent on the request are safe to act upon.
\nYour server should not ignore but handle these requests whenever you’re attempting to do cross origin requests.
\nA way to handle these to get comfortable is to ensure that for any path with OPTIONS method the server sends a response with this header
\nAccess-Control-Allow-Origin: *
\nThis will tell the browser that the server is willing to answer requests from any origin.
\nAccording to the CORS strategy You can’t just force the browser to stop sending OPTIONS request if it thinks it needs to.
\nThere are two ways you can work around it:
\nSimple request
\nA simple cross-site request is one that meets all the following conditions:
\nThe only allowed methods are:
\nApart from the headers set automatically by the user agent (e.g. Connection, User-Agent, etc.), the only headers which are allowed to be manually set are:
\nThe only allowed values for the Content-Type header are:
\nA simple request will not cause a pre-flight OPTIONS request.
\nSet a cache for the OPTIONS check
\nYou can set a Access-Control-Max-Age for the OPTIONS request, so that it will not check the permission again until it is expired.
\nAccess-Control-Max-Age gives the value in seconds for how long the response to the preflight request can be cached for without sending another preflight request.