One Canonical Hostname
0 Intentional IssuesThe www and apex hostnames resolve to one version through a permanent redirect. www_vs_non must not be reported.
Expected result: www_vs_non NOT DETECTED
Seed a scan at this path on either hostname of a custom domain and the other hostname answers a permanent redirect whose host is the preferred one. Each row below is the same rule written the way a different stack writes it. The query string selects the row; it is not a link a crawl follows.
?shape=(none)308 Location: http://fixture.test/fp-www-canonical-host308 is the permanent redirect Next.js and most modern frameworks emit. It is as permanent as 301.
?shape=protocol-relative301 Location: //fixture.test/fp-www-canonical-host?shape=protocol-relativeA URI-reference, not an absolute URL. It must be resolved against the requested URL before its host is read.
?shape=to-home301 Location: http://fixture.test/The path is dropped. #9 asks which HOST serves, not whether deep links survive.
?shape=explicit-port301 Location: http://fixture.test:80/fp-www-canonical-host?shape=explicit-portThe default port written out. The hostname is unchanged by it.
?shape=prefer-wwwapex: 301 Location: http://www.fixture.test/… · www: 200Choosing www. as the canonical host is equally valid. Only the direction changes.
?shape=control-no-redirect is the positive control: both hostnames answer 200, and #9 must be reported.
Part of /fp-head-url-fixtures.