Skip to content

Fail unresponded requests with a different error code #326

@anarthal

Description

@anarthal

We offer config::cancel_if_unresponded, which makes a request fail if it was sent to the server but never responded because the connection was severed. There is no way to know whether these requests were processed by the server or not. At the moment, async_exec completes with asio::operation_aborted for these requests. This makes it impossible for the user to know when this situation happened. We should create a new error code for this situation. See #324 for the discussion.

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