Skip to content

Support for uncommon HTTP Status codes and how to set custom headers? #15

@ghost

Description

Hi, we have a resource that takes a while to create and want to return HTTP 202, and in general want to follow the conventions laid out here: https://farazdagi.com/posts/2014-10-16-rest-long-running-jobs/.
See here for a discussion of HTTP and long running processes: https://softwareengineering.stackexchange.com/questions/316208/http-status-code-for-still-processing.

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