I would add a custom 404 processor that would allow for a redirect similar to how your doing a redirect now. That way you could log the 404 error at the same time as redirecting the client to the appropriate site. The logging would allow you to monitor authorized clients that are being redirected. Joseph -----Original Message----- From: Bryan Andrews [mailto:bandrews@xxxxxxxxxxxxxxxxxx] Sent: Friday, December 07, 2001 5:55 AM To: [ISAserver.org Discussion List] Subject: [isalist] Client and destination Sets and Querystrings http://www.ISAserver.org Our company is using Digital Dashboard Technology for our client portals. We have a url such as: http://portal.oursite.com/Dashboard/dashboard.asp?DashboardID=http://por tal.oursite.com/DAVCatalog/Dashboards/Welcome/Focus/someclient/clientpor tal that renders from a redirect at: http://portal.oursite.com/clientportal We allow access to the client portal based on a client and destination set (so only the client can get in from their building). My question is that all of our client portals will render with the above URL just a different query string tacked to the end. Can I create destination sets that include the query string in the criteria? Otherwise I will be stuck having add every client to the destination set of http://portal.oursite.com/* Thanks for any thoughts ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: cismic@xxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')