It does not provide a cure for cancer, because its job is simply to inform the user suffering an issue that the experienced issue is not strictly on the server side but depends on the client side. Which appears duly, as a first step in troubleshooting. It informs the user that there are configurations that avoid it, so the user has an orientation to possibly check for alternatives, assess and reconsider local configuration. More details (works on this and that) are avoided for obvious privacy reasons.
In the new titles I saw an "is site s down": the information "works here", which you seem to be calling avoidable, is in fact a basic troubleshooting step to reconstruct where the issue is.
In the new titles I saw an "is site s down": the information "works here", which you seem to be calling avoidable, is in fact a basic troubleshooting step to reconstruct where the issue is.