Sorry I think what you’re asking is a little vague.
Are you saying that if you browse to, for example, www.mysite.com, you would like people to be redirected to www.mysite.com/directory/welcome.html?
Or are you saying that if you browse to www.mysite.com/directory/welcome.html, you’re being redirected to www.mysite.com?
Or are you saying that if you put [[~2]] in a document, it’s generating "/" as the URL instead of "/directory/welcome.html"?
OK that makes it clearer, thanks.
For your first request, I’m guessing (someone else may be able to correct me here) that you’ll need to redirect requests for / to /directory/welcome.html at the Apache level.
I can’t say I’ve noticed your second issue - I’ll give it a try on my install when I get home later this evening.
I don’t want to do a redirection in the apache level under the .htaccess file, because if my customer change the alias I must update the .htaccess file.
My solution is:
WEB (context)
directory (1)
welcome (2)
about (3)
site_start = 1
using the FirstChildRedirect in the #1 ressource, and it work !! but, I don’t like this method.
Simple question:
Why a ressource (alias) named /mypage.html is remplaced by the ’/’ if this ressource is the site_start value !!
Low
Low
Well, I use context for multiple domains, and for each context, I use a site_start (maybe a bad solution).
At the root, just one ’content’ ressource as site_start and the FirstChildRedirect snippet, well, it work.
If my site_start is, and for all my site/context define as 1, an error occur when I reach the root level of each domain.
I would like to disabled the redirection to the ’/’ when I call the url of the site_start ressource, impossible ?
Low