Use of OPTIONS in /core/http-methods (is OPTIONS a 'standard' HTTP method?)

[lathoub]

Reading /http-methods I'm unsure if OPTIONS is a 'standard' method (or 'other' method as described here) (It is not a 'optional' method).

Upcoming OGC API - Features - Part 4: Create, Replace, Update and Delete (in draft) has a requirement for the use of OPTIONS.

Requirement 15 A:
The server SHALL support the HTTP OPTIONS operation at each resource endpoint

If I read the text correctly, only apply 'standard' HTTP methods (GET/POST/PUT/PATCH/DELETE). OPTIONS is (again, according to the text) an 'other' method and thus not allowed.

The test code however allows OPTIONS as a standard method.

Is OPTIONS a standard method and thus allowed?

[sergei-maertens]

I would say so, considering the entire CORS mechanism in browsers depends on them.

Interestlingly the test code also checks for TRACE, which is also not mentioned in the published text.

[dvh]

I would say yes, and just follow the OpenAPI standard which supports GET/POST/PUT/PATCH/DELETE/OPTIONS/HEAD/TRACE as mentioned in #629