Yeah, you’re missing something, or else your a newb as well. Good thing about being a newb is that you’re not always going to be one!
As HTTP URLs go, the url-path is the part that goes after the hostname but before the query string or fragment identifier. It is shown in bold below.
As Scott demonstrates, you can map any url-path to a particular directory. However for each FTP user, you should make sure that you specify a subdirectory. For example if the home directory is /home/ajuarez, you should make a subdirectory called “public” or “web” and map the url-path to /home/ajuarez/public. Home directories are used to store various files and directories containing user information and should not be made web-accessible.
I am not sure I understand your question though, you are talking about two different things.
A redirect is where the web site tells the browser to fetch the content from a different URL. Since the browser has to fetch the content, the address the browser shows will change. The content can be on the same web site or a different web site.
A rewrite is where the web site changes the URL and then returns the content to the browser. The browser is not told what changes were made to the URL at all, and it does not have to make another fetch. Since the browser is not going to fetch a different URL, this will only work for that same website. You cannot have http://example.com/members/ re-written to http://members.example.com/ - since the hostname is different, it will be a redirect, and the visitor will see that http://members.example.com/ in the browser.
[color=#6600CC]Atropos[/color] | openvein.org