Skip to content

Determine how to handle connections which pass at the connecting stage but fail at the reading stage  #5867

@FestiveKyle

Description

@FestiveKyle

Some connections are successfully created but fail during reading of bytes after the HTTP request is sent. Examples of this can be found using the filters HTTPS Status Equals Info and Ciphers Does Not Equal Info.

How should results be shown for this? Currently the guidance page shows:

  • The banner stating "This service is not web-hosting..."
  • The Connection Results section has the Unreachable tag
  • Shows the TLS Results section with the expected results as those connections were successful.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions