If you set the absolute URL property of your site to "example.com" then the URL "www.example.com" will still work, e.g.
http://www.rollerweblogger.org/roller http://rollerweblogger.org/roller The absolute URL property was added to ensure that, no matter what URL is used to access your blog, the URLs generated by your blog will be consistent. Or maybe I'm missing some nuance here? - Dave On Oct 18, 2011, at 8:44 AM, Edd Grant wrote: > Hi Anil, > > Thanks for your response, it strikes me that many sites might want to > operate both with and without the 'www' sub-domain and may not wish to, or > be able to, perform the required redirect/ url re-writing configuration to > achieve this. Also, with the rising popularity of @font-face I wonder if it > might be sensible for roller to support being addressable at multiple URLs. > > Do you have a feel for the complexity of making such a change? If there was > a desire from others to have it then I'd be happy to take a look and see if > I can make the change if someone could point me in the right initial > direction in terms of the code-base. > > Cheers, > > Edd > > On 18 October 2011 14:33, Anil Gangolli <[email protected]> wrote: > >> Yes. If you don't set an absolute one, it stores the one from the initial >> request. >> >> --a. >> Sent from my iPhone >> >> On Oct 18, 2011, at 2:11, Edd Grant <[email protected]> wrote: >> >>> Hi All, >>> >>> My blog is served through 2 URLs: >>> >>> http://eddgrant.com/blog - for lazy typists :-) >>> >>> and >>> >>> http://www.eddgrant.com/blog >>> >>> Note: I have not set any value in the 'server settings | Absolute URL' >>> property. >>> >>> I recently noticed that whichever URL I hit first is then used by Roller >>> when generating URIs in templates through the use of >>> $url.resource(resource). This seems to happen until Roller is restarted >> at >>> which point the first subsequently served URI is used again. >>> >>> For example: >>> >>> If I start my server up and hit http://eddgrant.com/blog first then this >> is >>> used in subsequent calls to $url.resource(resource), conversely if I hit >>> http://www.eddgrant.com/blog first then this is the path that is used. >>> >>> I wouldn't usually be too concerned about this however I recently updated >> my >>> roller theme to use @font-face fonts, in doing so I have made a discovery >>> which I initially thought was a Firefox Bug: The issue being a same >> origin >>> restriction for served font files where the font file MUST be served from >>> the same domain as the CSS file in which it is enclosed. This is a pain >>> since it means that Firefox will only retrieve and render the font files >> on >>> one of my URLs at any moment in time, this of course makes my blog look >>> rather silly for visitors on the other URL :-( >>> >>> Server related options seem to be reconfiguring my server to redirect >> from >>> eddgrant.com to www.eddgrant.com, alternatively there is an >>> access-control-allow-origin header which I could set to remedy this. >> However >>> I wondered if it might be more elegant if Roller could be modified to >>> dynamically generate the URL during calls to $url.resource() based on the >>> requested URL. >>> >>> Anyone have any thoughts on this? If it would generally be considered a >>> useful requirement then shall I raise it as a feature request? >>> >>> Cheers, >>> >>> Edd >>> >>> -- >>> Web: http://www.eddgrant.com >>> Email: [email protected] >>> Mobile: +44 (0) 7861 394 543 >> > > > > -- > Web: http://www.eddgrant.com > Email: [email protected] > Mobile: +44 (0) 7861 394 543
