allowOptions

Property Manager name: Allow OPTIONS
Behavior version: The v2024-08-13 rule format supports the allowOptions behavior v1.1.
Rule format status: Deprecated, outdated rule format
Access: Read/Write
Allowed in includes: Yes

GET, HEAD, and OPTIONS requests are allowed by default. All other HTTP methods result in a 501 error. For full support of Cross-Origin Resource Sharing (CORS), you need to allow requests that use the OPTIONS method. If you're using the corsSupport behavior, do not disable OPTIONS requests. The response to an OPTIONS request is not cached, so the request always goes through the Akamai network to your origin, unless you use the constructResponse behavior to send responses directly from the Akamai network. See also the allowDelete, allowPatch, allowPost, and allowPut behaviors.

Option Type Description Requires

Option	Type	Description	Requires
`enabled`	boolean	Set this to `true` to reflect the default policy where edge servers allow the OPTIONS method, without caching the response. Set this to `false` to deny OPTIONS requests and respond with a 501 error.		{"displayType":"boolean","tag":"input","type":"checkbox"}

enabled

boolean

Set this to true to reflect the default policy where edge servers allow the OPTIONS method, without caching the response. Set this to false to deny OPTIONS requests and respond with a 501 error.

{"displayType":"boolean","tag":"input","type":"checkbox"}