School Information Technology Discussion <[log in to unmask]> writes:
>Help me understand.
It appears to me that this might be somewhat of a limitation in Doug's
content filtering solution. It looks like his filter is preventing all
access to the entire content at that IP address.
>>Because our URL filter blocks by IP address, it
>> will block all the sites on a server when one (or more) of the sites
>> the server hosts is deemed inappropriate.
There may be some content there that is inappropriate, but most filtering
solutions give an option to only block the specific url and not the entire
For example, we have a situtation where the entire tripod.com domain was
blocked because there are some inappropriate websites located there. One
of them was APPROPRIATE, so we added it to our whitelist of sites. A
whitelist is comprised of specific urls that the local can get to, in
spite of the blacklisted domain.
It can be approached in (at least) two different ways... block the entire
domain and open up specific urls within that domain. OR open the domain,
and block specific sites within it. Similar to port blocking (ie
firewalls) in that all ports can be blocked and then opened individually,
or all ports can be opened, and closed down individually.
The actual limitations and features are dependant upon the filtering
Chittenden South Supervisory Union
5420 Shelburne Rd. Suite 300
Shelburne, Vermont 05482
802.383.1234 x229 (v)
[log in to unmask]