Skip to content

Error structuring according to RFC7807 #133

Closed
@duebbert

Description

@duebbert

Have you considered RFC7807 (https://datatracker.ietf.org/doc/html/rfc7807) as a way of structuring errors? I haven't seen it much in the wild but I am always in favour of using standards where possible. Just wondering if you are aware of it and if so what arguments were against using it. Thanks!

Some projects that implemented it:
https://github.com/vapor-ware/fastapi-rfc7807
https://github.com/cbornet/python-httpproblem
https://github.com/dave-shawley/tornado-problem-details

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions