rob wrote:
With some of our more complex deployments i.e. where there are several
hops from Apache server to Apache server to roller, we are having some
problems with the hostname that gets pre-pended to some roller generated
urls.
Some generated urls are always relative, which we like and some are
absolute (the absolute ones can be problematic when the server "thinks"
it is on a different hostname than the client does.). I can't fathom
the logic as to why some are absolute and some are relative. A lot of
this logic is scattered around the themes ($url.site vs.
$url.absoluteSite) and also in URLModel.
you are right that it's a bit confusing at times and it would be nice to
not confuse things by offering lots of relative vs. absolute options.
The reason absolute urls are needed is because so much of blog content
goes into feeds which are not read back on the same host as the site, so
absolute urls are necessary to ensure everything is properly referenced.
If you have relative urls to anything in a feed that resource will not
get properly located.
The fix we are considering is to have the urls always be relative unless
"Absolute URL to site" is set in the site settings. In that case ALL
links will be absolute with the setting used to generate the absolute url.
I would actually go the opposite route and prefer absolute urls for
everything. As described above, using relative urls can be problematic
now that so much of the content from blogs is not read by people
actually accessing the original site through a browser.
As for your problem, I don't see how absolute urls are causing problems.
What kind of deployment configuration do you have such that setting
the absolute site url doesn't ensure that everything works properly?
-- Allen
Does this make sense? What are we missing?
Thanks,
Rob
