We are currently running one domain with many subdomains for individual clients. These clients all have their own wishes for rewriting rules, and we would like to seperate these rules for each client's subdomain. If possible, we would like to seperate the web.configs.

Is there an easy way to do this in IIS7?


I think there are many ways to accomplish this (and likely opinions to go along with each) but I would do one of the two following:

Separate the application into various websites within IIS

  • Use separate folders with unique web.config files
  • Use separate application pools so each can be restarted without affecting any other sites

Use 3rd Party Applications like Helicon Isapi Rewrite version 3

If you have under 20 subdomains, I would go with the first option. Pros: free, Cons: more administration. But you still have better control over the application if the application pools are split up. This way if one is misfiring for some reason, you can restart that one without affecting the others.

Helicon makes a good product. We use both solutions in our environment.


  • Thank you for your answer. We already have Helicon Ape installed on our IIS, and I was wondering if we could keep it to that without having to buy Helicon Isapi Rewrite. We basicly want seperate htaccess files then for each client, and they shouldn't be able to affect each other. – Deniz Zoeteman Jul 8 '13 at 13:29
  • Is it possible to separate the application into various websites (for each subdomain)? That way you can use native IIS 7.0 / code rewrites instead of buying a bunch of ISAPI Rewrite licenses. I think this might be your only option to avoid the cost of buying more licenses. – Mike J Jul 8 '13 at 13:34
  • We would like to avoid that option as much as possible, as we have a lot of clients. – Deniz Zoeteman Jul 8 '13 at 13:46
  • Also it would be difficult to set up in the way we have our application, as the application itself is a general root application, and individual resources are allocated to clients' subdomains as folders. That's also why we would love to have a seperate htaccess or webconfig for every client without using seperate folders, as the individual resources folder don't actually contain anything related to the application, just things like pictures etc. – Deniz Zoeteman Jul 8 '13 at 13:56
  • Could you make a relative path to htaccess files in Helicon Ape? – Deniz Zoeteman Jul 8 '13 at 13:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.