The most common reason for blocked requests not showing in the website deny log is that they are logged in the Web Security Manager Generic website proxy (ID 0 in the overview). This is because the request is targeting an unknown host or is malformed in some other way.

For example, when you bind inbound traffic to an interface with IP address 192.168.10.10 and you configure Web Security Manager to proxy requests for www.mydomain.com and then try to access the website by entering the IP address (192.168.10.10) in the browser address field, the request will be rejected because the browser sends a request for the virtual host 192.168.10.10 not the virtual host www.mydomain.com you just configured.

If you want Web Security Manager to respond to the IP address (which is practical for test purposes but definitely not recommended for production), add the IP address to the virtual host aliases list in Services->Websites->ADC->Load balancing+Virtual host aliases.

Enable "Add HTTP/1.1 VIA header information" in Services->Websites->ADC->Load balancing. This should do it.

Microsoft IIS is configured not to allow NTLM authentication if a request is coming from a proxy server (as with Web Security Manager). If it sees a NTLM request coming thru a proxy server, IIS will subvert to other authentication methods, such as Basic of Digest.

If "Add HTTP/1.1 VIA header information" is enabled Web Security Manager will insert a Via: header in forwarded requests which will inform the back-end server that the request is proxied.

Enter a redirect rule in Services->Websites->ADC->Virtual host.

For example: To redirect visitors requesting http://www.mydomain.com/secret/someapp.php to https://www.mydomain.com/secret/someapp.php enter the following redirect rule:

Match Type: "prefix"

Match: /secret/

Redirect externally to: http://www.mydomain.com/secret/

This will redirect any request for resources in /secret/ to the HTTPS site.

Note that the protocol and server address is required in the redirect to field. It can be any address including https://www.myotherdomain.com/secret/deep/in/the/directory/tree/ in which case a request for http://www.mydomain.com/secret/someapp.php will be redirected to https://www.myotherdomain.com/secret/deep/in/the/directory/tree/someapp.php.

More advanced redirects are available using regular expressions see *redirect* in the manual or click *help* in the upper menu when you are on the server page.