Determine how to handle connections which pass at the connecting stage but fail at the reading stage
Open
bug
- Dominant language
- JavaScript
- Stars
- 39
- Forks
- 15
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 22
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.