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.

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

Make it clearer what "timeout" means as a status #404

Open
gwire opened this issue Aug 25, 2020 · 3 comments
Open

Make it clearer what "timeout" means as a status #404

gwire opened this issue Aug 25, 2020 · 3 comments
Assignees
Labels

Comments

@gwire
Copy link

gwire commented Aug 25, 2020

It's not clear to users what "timeout" means as a status when listed on a result page. My understanding is that an attempt to retrieve the page was unsuccessful, but that the failure could have been as a result of an error, rather than a proactive blocking attempt by the ISP.

There should be some expansion of this status, perhaps as a mouse-over info box?

@dantheta
Copy link

Added "no response received" description with popover. The timeout status is intended to convey a temporary error of a technical nature rather than imply the presence of network interception or tampering.

@dantheta dantheta self-assigned this Aug 25, 2020
dantheta added a commit to dantheta/blocked-frontend-py that referenced this issue Aug 25, 2020
@gwire
Copy link
Author

gwire commented Aug 26, 2020

Is there any way to embed some kind of history, eg the previous check result, to give some hint as to how temporary the state might be?

@dantheta
Copy link

we could show the timestamp of the last non-error result, though I'm conscious that the table is getting a bit crowded. We've generally got the last few months test results available online (older test results get archived from the DB), so we could click through to a page showing the test history for that url/network.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants