Re:A domain move disaster
by chrisseaton on Monday December 14, 2015 @07:21PM
(#10735043)
But http://domain.com and https://domain.com are two entirely different sites aren't they? They could serve totally unrelated content.
[ Parent
| on HN ]
Re:A domain move disaster
by michaelbuckbee on Monday December 14, 2015 @08:39PM
(#10735410)
In an extremely pedantic sense yes I suppose they could, but in practice this is so far on the fringes of things as to be a non-issue.
If you want to get really nitpicky about it you could restrict it to only cases where HSTS headers(of which Google + Chrome really took the lead with) are present.
You could also serve entirely different sites to chrome and to firefox.
Re:A domain move disaster
by artursapek on Monday December 14, 2015 @07:35PM
(#10735124)
I'm sure people try doing this with Googlebot... serving different content to it than to real "users". I wonder if Google tries to detect this by spoofing its user agent sometimes.
Re:A domain move disaster
by scott_karana on Monday December 14, 2015 @07:43PM
(#10735162)
I suspect it does, all the time, since it would get gamed frequently with fake filler content.
Re:A domain move disaster
by artursapek on Monday December 14, 2015 @08:11PM
(#10735299)
It's really fascinating all of the problems they must have to juggle in order to make their shit work. :D
Re:A domain move disaster
by JoshTriplett on Monday December 14, 2015 @07:27PM
(#10735078)
Technologically, yes. But a well-behaved site shouldn't do that; it breaks the expectations of both people and tools. Either serve the same content, or (even better) serve a redirect.
Re:A domain move disaster
by chrisseaton on Monday December 14, 2015 @07:31PM
(#10735101)
I can equally imagine someone being irate if Google treated them the same. Might as well at least be technically correct if you're always going to annoy half of the people either way.