config.absRefPrefix in the recent versions, so
config.baseUrl could be replaced in the future. What I propose for the future is that we use
config.absRefPrefix = auto by default, if not overridden or emptied (
config.absRefPrefix =) in frontend by custom typoscript. This ensures that new installations do not have to worry about that option anymore - it just works.
I would like to gather feedback in which cases
config.baseUrl would be superior to
config.absRefPrefix - because we (again) have multiple approaches to solve a common issue - and I’d like to show a best practice for Core.
Personal remark: We used
config.baseUrl in the past due to some websites 100% with flash (that was back then), but had problems with IE6 back then, and
absRefPrefix was not supported everywhere. This changed sometime in 4.x when we switched all our installations to
absRefPrefix = / (or auto) to generate absolute URLs, which works fine for around 100 projects we used this functionality back then. It might make sense for some static pages like newsletters, but then we use
config.absRefPrefix = http://email.mydomain.com.