Troubleshooting

Welcome Page Not Displayed

If the welcome page does not show up you should make sure that you access a URL without a path, and that your browser is correctly sending a User-Agent header, to ensure the criteria of the rule is met.
You can verify this easily with the default access log written by McAfee Web Gateway: [21/Nov/2011:11:00:10 +0000] "" 192.168.0.1 302 "GET http://www.google.com/
HTTP/1.1" "" "-" "" 2595 "Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1" "" "0"

Pay attention to the following fields:
• http://www.google.com/
This is the URL that has been requested by the client. Pay attention to the end of the URL string. The welcome page rule will only trigger if there is a “/” at the end of the URL. All other paths will be ignored.

• Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
This is the User-Agent header sent by the client. It must contain “mozilla” (case insensitive). Otherwise the rule will not match.
• 302
This is the status code that McAfeeWeb Gateway has returned. 302 is the expected status code for a redirect. However you need to be cautious, since the 302 status code may also tell that the web server has redirected the browser.

Welcome Page Never Times Out

If you see that a client only receives the welcome page once, but is never asked again, it may be related to the PDStorage key never timing out. As long as there are consistent requests made by a clients browser, it may not time out. In this case it may help to decrease the time out in PDStorage, or find out using the access log what URL is keeping the client alive.

Welcome Page Not Enforced

This example of the welcome page does not include a verification that a client has accessed, read, and understood the welcome page. When the Redirect action is called, the welcome page is treated as “Accepted”. There are further examples available which enforce the user to click a button to accept the welcome page before access to the Internet is allowed.