Skip to content

timeout does only a read timeout, not a connect timeout #24

Open
@kpmueller

Description

@kpmueller

The timeout configured in the client only uses s.setSoTimeout(timeout); -- this timeout only affects read

This means that the timeout does not change for connecting to the clamav host, as you would expect, which instead relies on the default timeouts. They can be very long.

I've created a patch to address this, which I believe works, but you would want to verify.

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