3 ms·
This is a UX problem, not a technical issue. I think you may be misguided in assuming that if the "www." portion was present to users that they would automatica
by engido9740 5y ago
This is a UX problem, not a technical issue. I think you may be misguided in assuming that if the "www." portion was present to users that they would automatically understand the issue at hand.
This is a false assumption. Your average user has probably never realized that "www." is not optional, and that with and without it are resolving differently.
This is very much a problem that you can, and should, solve FOR your users via properly configured DNS settings. Otherwise you're picking an odd hill to die on.
I promise I mean no disrespect. In fact, to put it another way, even if Chrome did what you said, it would not solve your issue - which is users failing to reach your site. Hope you can get it sorted with your provided, or switch to another. I've had good luck with Route53 via AWS.
- apostacy 5y ago> I think you may be misguided in assuming that if the "www." portion was present to users that they would automatically understand the issue at hand. It is a completely sensible assumption that the full domain name will be visible to users at all times. Google is the one who is making their browser do strange things like this that break the web.
- MiguelX413 5y agoIt is a completely sensible assumption that the full domain name will be visible to users at all times, but it is not a completely sensible assumption that even if it were the case that the whole URL were visible ithisn chrome, that it would solve the issue.
- i_cannot_hack 5y agoI don't expect Chrome to solve my issue with the broken url. I do, however, expect them to not make it worse by falsely presenting the broken url as a working url to the user (while hiding the one that actually works).