Hi Vernon,
I would add a few things to remind, when it comes to content switching scenarios, where the hostname and/or path needs to be changed.
1.) /blog/ would most likely contain nested ressources and may also reference to other sub directories. So it will be most likely the case that a
starts_with
operator have to be used, to make the entire path accessible.
2.) If the blog website is build on absolute pathes (e.g.
Click me
), then the site would nevertheless flip after the initial page is loaded. To fix this behavior, you have to change the delivered content using
[STREAM]
to reflect the changed host-header-value.
3.) If the blog website is build on root pathes that are different (e.g.
),
then
[STREAM]
needs to replace those links too.
4.) If the site is build on relative pathes (e.g.
), it will work most of the time, but only if you proxy to the path where the relativity starts.
@Mel: The best thing you could do, is to ask your provider to accept your desired HOSTNAME and provide every ressources below the path of /blog. In this case you won't need to dig into the website content and correct certain things...
Cheers, Kai