Is OPTIONS HTTP method supported on Azure CDN?

Miguel Garcia Lopez 0

We have an Microsoft CDN (classic) Endpoint setup backed by a Storage Blob Container.

Whenever an OPTIONS request is issued (due to a browser dealing with CORS), we are getting a 405 (method not allowed) response from the CDN. The response includes a x-ms-error-code: UnsupportedHttpVerb header and also allow: GET,HEAD.

We have setup CORS in our Blob service from the Storage account, allowing for all origins, headers and GET, HEAD and OPTIONS methods:

User's image

If, via curl for example, I try to do OPTIONS on the resource, I am getting the 405. This does however not happen for GET nor HEAD.

So, is OPTIONS supported at all for Azure CDN? Is there anything (else?) we should be configuring?

Thanks in advance!

SaiKishor-MSFT 17,236 Reputation points

2023-03-20T23:23:02.7566667+00:00

@Miguel Garcia Lopez I am reaching out to see if you have any further questions. If so, please let us know and we will be glad to assist further. If the below answer was helpful, please make sure to Accept it as answer as it helps other members in the community. Thank you!
SaiKishor-MSFT 17,236 Reputation points

2023-03-21T18:22:24.57+00:00

@Miguel Garcia Lopez Any update?

1 answer

SaiKishor-MSFT 17,236 Reputation points

2023-03-20T23:23:20.5433333+00:00

@Miguel Garcia Lopez Thanks for reaching out to Microsoft Q&A.

Have you set the Access-Control-Allow-Origin header to wildcard (*) or a single origin? Please refer here- https://learn.microsoft.com/en-us/azure/cdn/cdn-cors#wildcard-or-single-origin-scenarios
Please sign in to rate this answer.
Jayesh Kudukken Thazhath 1 Reputation point Microsoft Employee

2023-03-24T14:40:01.7666667+00:00

I am facing same problem and the documentation seems to be confusing, why do we get 405, is it coming from blob or CDN? if OPTIONS not supported how do even browser pre flight calls will work?

Miguel Garcia Lopez 0 Reputation points

2023-03-27T15:19:52.86+00:00

Yes, we have set the Access-Control-Allow-Origin indeed, and as a matter of fact it all works OK for example for the GET method. It is when we are using OPTIONS that we are experiencing this issue.

Marilee Turscak-MSFT 37,046 Reputation points Microsoft Employee

2023-04-19T19:26:51.3133333+00:00

It should be supported if your original host is responding to these requests as described here. Adding @SumanthMarigowda for additional context.

Macura, Jan 0 Reputation points

2024-09-05T15:31:20.9733333+00:00

Hi @Marilee Turscak-MSFT , I am facing exactly the same issue as described in original post from @Miguel Garcia Lopez . My CORS settings in Storage account are also set correctly.

And doing an OPTIONS request via postman ends up with:

Any thoughts?

Thanks in advance,

Jan

Miguel Garcia 0 Reputation points

2024-09-05T17:32:37.36+00:00

Hi, in the attached image it can be seen my configuration: Allowed Origins in Blob Service column is '*' indeed. Is this not enough? Thanks!

Macura, Jan 0 Reputation points

2024-09-05T17:58:26.9466667+00:00

I have the same as you do, but still the options requests fails with 405.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Is OPTIONS HTTP method supported on Azure CDN?

1 answer

Your answer