Skip to content

The default options responder does not take into consideration on_request, leading to allow='' #2671

Description

@CaselIT

When using on_request in a resource, the default options header will reply with an empty allow header.
This is wrong since the spec says:

An empty Allow value indicates that the resource allows no request methods, which might occur temporarily for a given resource.

sadly there does not seem to be a * to indicate all methods, but we can likely use the COMBINED_METHODS list in that case.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions