Skip to content

fix: add missing HTTP error types #144

@NeelMalwatkar

Description

@NeelMalwatkar

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Right now, only following error codes exist:

  • 400 BadRequest
  • 401 Unauthorized
  • 403 Forbidden
  • 404 NotFound
  • 503 ServiceUnavailable

Errors missing:

  • 405 Method Not Allowed
  • 409 Conflict
  • 410 Gone
  • 415 Unsupported Media Type
  • 422 Unprocessable Entity
  • 429 Too Many Requests
  • 500 Internal Server Error
  • 502 Bad Gateway
  • 504 Gateway Timeout

Desired Solution you'd like

Add error structs for the remaining common HTTP status codes.

Additional Context

No response

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