I'm trying to learn why OPTIONS method requests (presumably CORS preflight requests) are logged as 200 status while all GET method requests are logged as the expected 301 (moved permanently). The only thing being returned at that address is a Response.RedirectPermanent with the new address.
For context, the 301 has been in place for a few weeks, and in many cases the Referer URL has been gone a lot longer, so my first thought is that this is a scripted call. Except for these OPTIONS request, everything else hitting the specific URL I'm looking at have telltale signs of automation like coming from long-gone Referers. With these OPTIONS requests, frequently a given address in the log will only make that one call to the server and then nothing ever again. So the pattern suggests its a proxy for some form of automation. Again, this paragraph is just for context, it's not the question itself. I'm not worried about potential automation.
Getting back to the question - why do these OPTIONS requests show up as 200 in this circumstance? Ultimately the reason I'm trying to find out why is because I want to know if I need to do anything to accommodate these requests properly or if this is just expected behavior for this type of request to a permanent redirect.