Skip to content

Improve transport error classificationΒ #1773

Description

@cstamas

New feature, improvement proposal

Currently we support "not found" and "other" errors, nothing more.
We may want to improve this, plus, add extra informations about errors, like is the request retryable, etc.

For example: 410 Gone would be classified as "other".

Activity

  1. kwin commented on Jan 28, 2026

    @kwin
    Member

    I would start simple by classifying 410 as not found (cached). Having more than those two existing classifications with potentially configurable caching behavior requires more changes.

  2. cstamas commented on Jan 29, 2026

    @cstamas
    MemberAuthor

    Agreed: lets update HTTP transports and make them handle 404 and 410 the same.

  3. added 2 commits that reference this issue on Jan 29, 2026
  4. linked a pull request that will close this issueGH-1773: Treat 410 Gone as 404 Not Found #1774on Jan 29, 2026
  5. added a commit that references this issue on Jan 29, 2026
  6. added a commit that references this issue on Jan 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions