Canonical redirection broken for empty host in 'home' option

[thenlich]

The canonical redirection of the host part (e.g. www.example.com vs example.com) is broken if get_option('home') returns an empty host part. It returns an invalid redirect in this case.

Setting the 'home' option to an empty host name (e. g. '/') is necessary if the blog needs to be reachable from different domains or protocols (HTTP/HTTPS) without redirecting to a particular one, or when the resulting HTML output should be relocatable (not contain protocol nor hostname).

[Otto42]

This seems to me to be very much an edge case that would be better handled by simply disabling canonical redirection entirely, via a plugin or something.

[thenlich]

Such an option would be useful. It would be even better to (optionally) disable redirection not entirely, but selectively (for scheme:/host/path).

But that is independent from this bug: if siteurl does not contain a hostname, we cannot rewrite to it. But since a redirect needs an absolute URL, we must use the original from the request in this case.

[jergendutch]

This feature is sorely needed by people using wordpress in a development/staging versus live environment where the same config must be used in both places, and so live should not get a development hostname by accident.

[markjaquith]

if siteurl does not contain a hostname, we cannot rewrite to it

True. So it's a good patch from a CYA perspective, even if your intended use is unorthodox.

[markjaquith]

(In [7916]) Do not use the "home"-supplied host for canonical redirects if no host is there specified. props thenlich. fixes #6890