Hierarchal Web.Config
I've a strange problem, I want to allow access to my blog using http://blog.ayende.com/ but the way that sub domains are implemented on my host gets in the way. The problem is that it's possible to access sub domains by doing: http://www.ayende.com/blog/, so in essense I've two physical paths to the same place. Usually it means that I would've to take care for paths in the html, but here I've another problem.
The root site, http://www.ayende.com/ runs Cuyahoga and this require that the blog application (dasBlog) to remove several httpModules in its own web.config. That didn't cause troubles so far, but now that I want to change the path, I'm getting very nasty error about the non existing httpModules that I'm removing.
So right now I can either:
- Remove the entries from the web.config, which will enable blog.ayende.com but not www.ayende.com/blog
- Keep the entries, which will kill www.ayende.com/blog but enable blog.ayende.com (and better seperation between the applications).
Any suggestions how to make it work? Currently I'm going with the second method so as not to break links.
Comments
Comment preview