Friendly URLs question again (Are URL rewrites possible on TS/LS preview):

PRK

TS/LS 7.2.1 on a .NET platform
Preview: IIS 7.5 Runtime: IIS 6

I know this has been brought up quite a few times on the forum, but is there a good solution to implement this? (apologies for bringing this up again!!)
I have to take out the site-name from the page urls and also, if possible, hide the .page extensions. I understand there are two parts to implement this
1. Implement url re-writes at the runtime server (IIS 6 in this case)
2. Use url alias in TS/LS to map page names to friendly names/paths
However, the TS 7.2.1 installation (installed on the .NET platform) that I am working on, apparently does not support the ootb URL alias feature (came to know this through support). Hence I was wondering if URL re-writes could be used both at the runtime environment and at the preview environment; please let me know if this seems feasible or if someone has already implemented this.
Another issue would be handling intra-page links, populated using page tokens like $url_prefix, these page tokens include the site-name in the links, however, I think this can be handled by doing away with the page tokens and coding the appearance part in a suitable manner, or this could be handled by having custom beans for the concerned page tokens to make them not include the site-name.
Please help.
Thanks and regards,
PK

Bowker

Ok, so we are doing both of these.
1 - in our front-end web server (Apache) (not the App server that LSDS runs in) we examine the host name and do a proxy to LS inserting the "site" name. For example:

RewriteCond %{HTTP:host} ^m\. [NC]
RewriteRule ^([^.]*)$ http://localhost:1776/s1Mobile$1?%{QUERY_STRING}

In this case if the URL's host starts with "m." we send to [livesite]/s1Mobile (s1Mobile is our site name) passing along the rest of the url and any query string.

2 - We are using OOTB Alias URLs in TS 7.2.1. They are only supported with .page files and not externals.

(This is the end of "what I've done". Now begins what I plan to do)
3 - You asked about 'intra-page' what I think you mean is inter-page links (i.e. Linking from one page to the other). I plan on using <a href="$URL_ALIAS(put alias here)">...</a> I will be using $URL_PREFIX for objects (such as images) on a page.

Note:
We have a requirement to create "campaign" links which are short, easy to remember/type URLs that ultimately link to either a page file or external URL BUT it needs to append a parameter to the end. For example, if the campaign is for "sales" they want http://www.site.com/sales to really display http://www.site.com/corporate/marketing?campaign=salesLead.

If you have a solution to that, let me know. My solution is NOT PRETTY. It involves a site pre-controller that will be hit on every page to look through all the all the campaigns currently active and if it finds one issue a 302.