5 ms·
But http://domain.com http://domain.com and https://domain.com https://domain.com are two entirely different sites aren't they? They could serve totally unrelat
by chrisseaton 11y ago
But http://domain.com http://domain.com and https://domain.com https://domain.com are two entirely different sites aren't they? They could serve totally unrelated content.
- JoshTriplett 11y agoTechnologically, 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.
- chrisseaton 11y agoI 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.
- Buge 11y agoYou could also serve entirely different sites to chrome and to firefox.
- artursapek 11y agoI'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.
- scott_karana 11y agoI suspect it does, all the time, since it would get gamed frequently with fake filler content.
- artursapek 11y agoIt's really fascinating all of the problems they must have to juggle in order to make their shit work. :D
- michaelbuckbee 11y agoIn 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.