Skip to content

Make UserCanceled Alert Warning not be tracing::warn! #2182

@TroyKomodo

Description

@TroyKomodo

Checklist

  • I've searched the issue tracker for similar bugs.

Describe the bug
A clear and concise description of what the bug is.

When running our server for hours we get warning logs from rustls

{"timestamp":"2024-10-26T14:36:31.330816392+00:00","level":"WARN","fields":{"message":"TLS alert warning received: AlertMessagePayload { level: Warning, description: UserCanceled }","log.target":"rustls::common_state","log.module_path":"rustls::common_state","log.file":"/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.23.14/src/common_state.rs","log.line":519},"target":"rustls::common_state","filename":/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustls-0.23.14/src/common_state.rs","line_number":519}

warn!("TLS alert warning received: {:?}", alert);

To Reproduce

Not sure.

Applicable Version(s)
A list of versions and platforms you've tested with.

v0.23.14

Expected behavior

We are unsure if these warnings are meaningful? Is there something on our end that we should fix? How do we know if this is an issue or if we should just silence them?

Additional context
-_-

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