Take "/*" out of the path field. HTTPS connections can't be evaluated on the path, so if one is specified, the whole site is HTTPS-denied. Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison/ Read the books! ----- Original Message ----- From: "Graham Walsh" <graham.walsh@xxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Monday, April 22, 2002 5:58 AM Subject: [isalist] HTTPS Sites http://www.ISAserver.org All I have a customer that wants to block all sites apart from a destination set that contains the sites they want the call centre people to access to process credit card details. When I enable the S&C rules, the users can access the normal sites but not the HTTPS part of the site. In the Destination Set what should I be putting, eg www.securetrading.net or https://securetrading.net with the path of /* The config is W2k, ISA SP1 and NT4 Clients with the FW client installed. Your help would be much appreciated. Regards Graham ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')