|Posted: 02 September 2011 at 10:04am
We're currenly evaluating helicon ape, specificially the isapi rewrite functionality for use with a dotnetnuke site.
We have 4 portals with different domain names / ip's on a single instance of IIS/DNN. We have a VirtualHost section set up in the httpd.conf file for each of the ips/domain names.
What seems to be happening is that the first two of the virtualhost sections work without issue. If we create a 3rd or 4th section for the remaining sites, those sections will work only up until we access either the 1st or 2nd sites referenced in the 1st two virtualhost sections. It seems like some sort of caching issue related to running multiple domains/ips from the same IIS instance.
Is this a limitation of the trial version? Is this behavior expected?
We've specified a RewriteLog per VirtualHost. The way we've figured out that IP/Domain requests are ending up in the wrong VirtualHost group is because we're seeing log records like these in a file for a single VirtualHost group.
220.127.116.11 18.104.22.168 [02/Sep/2011:09:09:53] [22.214.171.124/sid#2]....
126.96.36.199 188.8.131.52 [02/Sep/2011:10:09:10] [184.108.40.206/sid#2]....
220.127.116.11 18.104.22.168 [02/Sep/2011:09:09:42] [22.214.171.124/sid#2]....
Our VirtualHost groups look like this with the ips specified.