> You could send different websites based on what port the request comes from.

But that's you controlling that, as the person running the website.

When it's the user controlling it, by setting which domain to visit, that's in their control, so they need to see it in their UI.

If you're going to reduce to the absurdity of 'anyone could serve anything from anywhere' then why show a domain at all? ebay.com could serve me the content of google.com, so let's not bother with domain names? Is that your argument?

The person controlling the website is responsible for making www and non-www show the same thing, as well as making http and https show the same thing. (Redirects are fine.) A user's ability to affect something doesn't automatically mean it's their responsibility.

I'm not making an argument about what should be shown right now, I just think your argument, based on what "might be different", is pretty flawed.

> The person controlling the website is responsible for making www and non-www show the same thing, as well as making http and https show the same thing. (Redirects are fine.)

But there's no standard that requires this, that I'm aware of.

Chrome are acting like there is, but I believe there isn't.

There's no standard that says you have to deliver the same data to anyone as far as I'm aware. It's still an absolute abomination if http and https are different sites, for example.