Posted: 18 September 2011 at 7:08am | IP Logged

Hello,

We need to make large amount sub domain URL redirect like this:

RewriteCond %{HTTP:Host} ^www\.mydomain\.com$
RewriteRule ^city1/community1.aspx$ http://city1.mydomain.com/ [NC,L,R=301]

RewriteCond %{HTTP:Host} ^www\.mydomain\.com$
RewriteRule ^city2/community2.aspx$ http://city2.mydomain.com/ [NC,L,R=301]

We found for each RewriteRule, there has to be a RewriteCond ahead of it. Considering the large number of redirect, is there more efficient way to implement these?

Also, currently there are already a few hundreds of flat RewriteRules, and using of mapfile of hundreds of pairs of query strings. what's the best way to manage them, such as prevent unexpected redirect from happening?

Thank you in advance for your advice!

John

Posted: 20 September 2011 at 9:37pm | IP Logged

Hey Andrew,

Thank you for your response!

Actually, city names are all different, and community names are also different. The only pattern is we want to substitute www with sub-domain name, like city names. Other parts of the URL's vary.

It looks if using 2 variables, one in place of cityname, the other for the rest part after cityname/ would solve the problem. Is it doable?

Thanks again for your help!

John

Posted: 21 September 2011 at 8:35am | IP Logged

yes, "community" part is the problem. It would need to be redirected to the same communityname under destination URL.

So, is this valid? -

RewriteCond %{HTTP:Host} ^www\.mydomain\.com$
RewriteRule ^([^/]+)/([^./]).aspx$ http://$1.mydomain.com/$2 [NC,L,R=301]

with expecting $2 reflect ([^./]).aspx part. I kind of doubt it. Or is there such capacity for the rewriter at all?

Appreciate your help, as always!

John

Posted: 22 September 2011 at 9:09am | IP Logged

Thank you, Andrew!

Logging is another question I'd like to ask - what level should I put there? We want to have enough info but don't want to see the log file size grow too fast.

Thanks,

John