Re: cant anyone look at this?
- From: Jeff Herr <Jeff.Herr@xxxxxxxxxxxxxxx>
- To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 22 Aug 2001 09:28:54 -0700
i agree the approach will work.
but... i am more interested in how to deal with the apparent inability to
define content type.
Jeff Herr IT Manager
http://www.teleplan-ca.com
8875 Washington Blvd, Suite 'B'
Roseville, California 95678
916.677.4538
-----Original Message-----
From: John Watson [mailto:jwatson@xxxxxx]
Sent: Wednesday, August 22, 2001 8:43 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Re: cant anyone look at this?
http://www.ISAserver.org
Well....
I think Yahoo just doesn't have a MIME type and no amount of looking for one
will find one.
However, you might try this:
- Create a destination set with *.yahoo.com specified, call it Yahoo
- Change your primary site and content rule to except the Yahoo destination
set. Configure the HTTP Content to whatever types you like.
- Create a new site and content rule for only the Yahoo destination set.
Set it's HTTP Content to "All Content Groups".
-John.
----- Original Message -----
From: "Jeff Herr" <Jeff.Herr@xxxxxxxxxxxxxxx>
To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
Sent: Wednesday, August 22, 2001 10:48
Subject: [isalist] cant anyone look at this?
> http://www.ISAserver.org
>
>
> assume: basic setup is working with single site/content rule.
>
> go to site and content rule you use to allow anyone access to anywhere
> anytime. Dont we all have one?
>
> select HTTP-CONTENT tab.
>
> under "apply this rule to" deselect "all content groups"
> and choose "selected content groups"
> and insure that ALL CONTENT TYPES are enabled.
>
> now, as example, all yahoo pages other than their home page yield a 12202.
>
> obviously this is due to their content type not being defined...right?
> how do you define something for them?
>
> This type of undefined content is shown at UNKNOWN in the reports too.
>
> rather that have all content allowed, i would like to allow only those
> specified and selected.
> but how to go about defining these currently "un-defineable" types?
>
> are they not ABLE to be defined? this would indicate a real loss of
product
> value.
>
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org Discussion List as:
jwatson@xxxxxx
> To unsubscribe send a blank email to $subst('Email.Unsub')
>
>
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jeff.herr@xxxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
