Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
FestiveKyle opened this issue Nov 6, 2024 · 0 comments
Open

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

FestiveKyle opened this issue Nov 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@FestiveKyle
Copy link
Collaborator

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.
@FestiveKyle FestiveKyle added the bug Something isn't working label Nov 6, 2024
@FestiveKyle FestiveKyle changed the title Determine how to handle connections which pass at the connections stage but fail at the reading stage Determine how to handle connections which pass at the connecting stage but fail at the reading stage Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FestiveKyle