Having trouble restricting access to virtual multihosting entry

Question

Hi,
I've created a new proxy instance with all default settings. I'm trying to use virtual multihosting with an ACL to restrict access to this virtual multihost. I'm having troubles and am not able to block it. I thought I could use a template to impose this, but perhaps I'm wrong. Here's how I've done it:
I've created a single template called "testing-access", containing:
http://testing\.mydomain\.com/.*
I've then added a single Virtual Multihost entry as follows:
Source Hostname (alias): testing
Source Domain Name: mydomain.com
Destination URL Prefix: http://testing2.mydomain.com
Use This Template: testing-access
At this stage, the virtual multihost works. I can access testing2.mydomain.com via testing.mydomain.com.
Now I go to implement the ACL to, for testing purposes only, Deny all access to this virtual multihost. Remember this just testing to learn how to apply an ACL to a virtual multihost. Later, my intention is to block all http access (by way of Deny applied to http://.* resource ACL) via the proxy, except for the virtual multihosts. These virtual multihosts will also include access control based on different IP addresses. The thought is to have a different template for each virtual multihost then apply a set of ACE Allow conditions for the template's ACL.
I go into Administer Access Control, select the "The template 'testing-access'" resource. I then click on Edit and add the ACL as follows:
Action: Deny
Users/Groups: anyone
From Host: anyplace
Rights: all
Extra: N/A
Continue: enabled
I restart the server instance then attempt to access the virtual multihost, which I can. I cannot understand why this is not being blocked.
I've tried changing Continue to be disabled but that hasn't helped either. It seems as though the ACL for http://.* (which incidentally by default has no ACL) is taking precedence. I've also tried adding to the template without success: http://testing2\.mydomain\.com/.*
If I were to add an ACL to http://.* resource to Deny it blocks all http://.* requests. This is no good because effectively what I would like to do is block all http://.* access EXCEPT for those virtual multihosts I add. Each virtual multihost will need to have its own ACL to restrict based on IP. This is why I created a template for the one above. The objective would be to add several Allow ACEs depending on host, such that only those who are on this ACL can access the URL in the template (a virtual multihost, remember), anything else is blocked via the http://.*
I only did the test at the top to learn how to successfully implement an ACL on a reverse multihost, by applying a Deny for everyone via the template ACL.
Any ideas?

Answer 1

In the case structure you can replace the 'success' button with the vi that you want to run. If you set the properties of the vi to 'show front panel when called' it will open and run when a log-in is successful.
There are other ways to do this, this is one of the more simple ways.
Ian