Skip to content

Handle BEP 3 HTTP tracker failure responses #199

Description

@artrixdotdev

HTTP tracker responses may contain a failure reason string instead of interval and peers. Add explicit decoding/handling for failure reason so tracker errors are surfaced cleanly instead of failing as a generic bencode/shape error; see the tracker response requirements in BEP 3.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions