On Mon, 11 March 2002, "Jay Turner" wrote > intel.com > program.intel.com > > Now looking at this, would you agree that I > should be able to go to anything that is in > the intel.com domain/subdomain (www.intel.com, > developer.intel.com etc) as well as being able > to go to program.intel.com?
Actually Jay, I think this makes perfect sense as it is. It is appropriate that the single entry <intel.com> in a whitelist would give access to all urls at <intel.com> and all subdomains; the <intel.com> *domain* being the "least common denominator" (if you will). In my opinion, adding <program.intel.com> redefines the "least common denominator" to the <program.intel.com> *subdomain* level. As you correctly stated, the entry <intel.com> in a whitelist gives access to <every.sub.domain.intel.com/and/every/url>. If your goal was to allow your users to " ... go to anything that is in the intel.com domain/subdomain (www.intel.com, developer.intel.com etc) as well as being able to go to program.intel.com" you would accomplish that by putting <intel.com> in your whitelist. If you stop and think about it, knowing that <intel.com> gives access to it all, specifically adding access to <program.intel.com> implies that there are other subdomains that are not allowed. Makes sense to me. Rick Matthews
