Skip to content

Improve HTTP status codes for server responses #12

@chocolatkey

Description

@chocolatkey

Right now, a lot of errors when using the server just return as error 500, which is not necessarily the "correct" code to be returning. For example, when a non-existent publication is requests, error 500 is returned, which is not very helpful compared to a 404. Or when an invalid path is provided, this is also a 500, when it should be 400.

Metadata

Metadata

Assignees

No one assigned

    Labels

    serveRelated to the serve command

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions