mod_rewrite

I just signed up for unlimited subdomains, being under the impression that you could bind subfolders to subdomains. I need subdomain.domain.com to point to www.domain.com/subdomain. The problem with the example in the kb is that it falls apart when you start talking about www.domain.com/subdomain/subfolder, you will get a 404. Most popular ASP.net based URL rewriting engines only handle the path after the servername, and while you can roll your own in an httpmodule, aparently Context.Rewrite mucks with your form targets. There are a handful of ISAPI solutions, but none of them are managed, so it would be impossible to add them in a shared environment.

I would really like this to be resolved ASAP, paying 60$ for a years worth of *.domain.com in my DNS table is kind of a ripoff.

 

There are multiple methods you can use to do this.
Search http://www.codeplex.com and use my ASP.NET Google Coop:
http://www.google.com/coop/cse?cx=009244845836111659857%3Albvxsjj8mho

You should find multiple code examples.
Salute,
Mark

 

You can find multiple URL rewriters for the ASP.net pipeline, that all suck in different ways. Implementing this functionality as an httphandler/httpmodule is a hack, any way you look at it. But anyways, those kinds of things will work (albeit with a few gotchas) if you are talking about turning domain.com/Products?name=tshirt into domain.com/Products/tshirt. When you are talking about turning domain.com/subdomain/subdir/Default.aspx into subdomain.domain.com/subdir/Default.aspx, you are talking about IIS modules. If you could find a managed module that could do the job, point me to it. The only modules I have found with any credibility are ISAPI ports of apache's mod_rewrite (like this, which incidentily is one of the few that has a good reputation http://www.micronovae.com/ModRewrite/ModRewrite.html)

All I am saying is that if you are going to offer subdomains, then go the next step and make it actually be useful. I will admit, I didn't do enough research before I came over here, so it is my own fault. Overall I think this is a fantastic host, but this is some functionality that is downright nessicary for alot of people who do freelance/consulting work for smaller businesses.

 

I think any module or ISAPI filter can be considered a "hack" and does not create a true subdomain site. There are limitations and gotchas even on these. The only way to accomplish a true subdomain site is to be a separate IIS site.




Aristotle

DiscountASP.NET
www.DiscountASP.NET

 

So my question is, why isn't this allowed? It's no extra stress on the server, and it's incredibly easy to set up in IIS. Back when I had my own server to host stuff on, it took me about half a minute to bind a subdomain to a subdirectory. I need blog.davesorrell.com to point to davesorrell.com/blog, but not actually include the '/blog' in the URL, since that screws up the software that's in that folder. I can't do much about it right now because of that minor flaw. I really feel like I'm throwing money away with the subdomain package, especially when the subdomains don't work the way they should.

 

Creating a site in IIS that points to a subdirectory of another site can cause problems. For example, when installing FrontPage extensions to the subdomain it conflicts with the extensions on the main domain. Also, how do you consolidate logging and stats, etc. It becomes a hosting nightmare. The simplest solustion isif you want separate content for a subdomain, you'll have to order a separate hosting account for that subdomain.


Aristotle

DiscountASP.NET
www.DiscountASP.NET

 

Then how would I go about cancelling the subdomain addon? Since it clearly doesn't do what the name suggests, I have no desire to throw my money away on something I can't use.