Skip to content

CORS requirements #72

@geira

Description

@geira

I see CORS errors popping up when trying different EDR beta services. We should mandate how to implement this to avoid later hassle.

Should be sufficient if services returned the following headers in each response:

Access-Control-Allow-Headers: Origin
Access-Control-Allow-Methods: GET
Access-Control-Allow-Origin: *

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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