Hi Rick, Thanks for your reply, comments below.
>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. OK, I initially thought that it may work purely on the fact that intel.com is listed so everything under that domain will be accessible including program.intel.com, which just so happens to be in the list also. >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. That makes sense, and I assumed that was the case, I just wanted some confirmation from the list. All it means is that I will have to do some further refinements to my whitelist removing all subdomains and just listing the top level domain (ie intel.com) or go through and explicitly list all the subdomains of a site (www.intel.com, developer.intel.com, program.intel.com etc..) Thanks for your feedback Regards Jay Turner >Makes sense to me. >Rick Matthews
