[quote]For example, a popular link is:
I want this to be redirected to http://www.hestakaup.com/index.php?option=com_content&task=view&id=13&Itemid=35[/quote]
This excerpt (from an excellent resource on using .htaccess, published by Earthlink/Mindspring, should point you in the right direction:
Syntax: Redirect [ status ] url-path url
The status argument is only available in Apache 1.2 or later.
The Redirect directive maps an old URL into a new one. The new URL is returned to the client which attempts to fetch it again with the new address. Url-path a (%-decoded) path; any requests for documents beginning with this path will be returned a redirect error to a new (%-encoded) url beginning with url.
Redirect /service http://foo2.bar.com/service
If the client requests http://myserver/service/foo.txt, it will be told to access http://foo2.bar.com/service/foo.txt instead.
Note: Redirect directives take precedence over Alias and ScriptAlias directives, irrespective of their ordering in the configuration file. Also, Url-path must be an absolute path, not a relative path, even when used with .htaccess files or inside of sections.
Returns a permanent redirect status (301) indicating that the resource has moved permanently.
Returns a temporary redirect status (302). This is the default.
Returns a “See Other” status (303) indicating that the resource has been replaced.
Returns a “Gone” status (410) indicating that the resource has been permanently removed. When this status is used the url argument should be omitted.
Other status codes can be returned by giving the numeric status code as the value of status. If the status is between 300 and 399, the url argument must be present, otherwise it must be omitted. Note that the status must be known to the Apache code (see the function send_error_response in http_protocol.c).
Syntax: RedirectTemp url-path url
This directive makes the client know that the Redirect is only temporary. (Status 302). Exactly equivalent to Redirect temporary
Syntax: RedirectPermanent url-path url
Context: directory, .htaccess
This directive makes the client know that the Redirect is permanent. (Status 301). Exactly equivalent to Redirect permanent [/quote]
Translating the above to your situation:
RedirectPermanent /joomla http://hestakaup.com
when placed in an .htaccess file located in the “base” directory of shirson.com (the directory within which the “joomla” directory resides), will cause the following to take place:
If the client requests http://www.shirson.com/joomla/index.php?option=com_content&task=view&id=13&Itemid=35 , it will be told to access http://www.hestakaup.com/index.php?option=com_content&task=view&id=13&Itemid=35
Which is what I believe you want to do.
Place it in the “top” web accessible directory of shirson.dom (on Dreamhost, the directory is probably named “shirson.com”). As .htaccess files impact all directories below them in the directory tree, that is all that is needed to impact the “joomla” subdirectory of shirson.com. Once this is done, there is no need to leave anything in the joomla sub-directory (that means files, and other directories). Test it first to make sure it is working as expected, then you delete all the other stuff.
This method works particularly well in your situation, because you should not experience any google penalty for doing it this way, and users that have existing links won’t be left “stranded”. Additionally, this allows you to go ahead and further develop shirson.com with freedom (just make sure and leave that line in whatever .htaccess file you ultimately end up using in the shirson.com directory. Good Luck, and let us know how it all works out.