Skip to content

Options configuration #1

Description

@bredele

OPTIONS is mostly used for pre-flight request. It means with request having HTTP verb other than GET/HEAD/POST (such as DELETE).

We should be able from the schema to define cors for GET/HEAD/POST similar to OPTIONS. Here's an example I have in mind:

{
  get: {
    '/': {
      options: {
        origin: 'http://mydomain.com'
       }
     }
  }
}

The options field will customize the OPTIONS method but also add a middlewae for GET/HEAD/POST.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions