RE: Blocking HTTPS
- From: "Jim Harrison" <Jim@xxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Mon, 31 Oct 2005 16:37:39 -0800
MW
Stop
Chopping
The
Thread
ISA ignores the protocol portion of the URL, so that won't work.
If you entered the data *as I specified*, this would work.
Create a destination that uses:
*.google.com & google.com in the "name or IP" field
..and
/accounts/* in the "path" field.
-------------------------------------------------------
Jim Harrison
MCP(NT4, W2K), A+, Network+, PCG
http://isaserver.org/Jim_Harrison/
http://isatools.org
Read the help / books / articles!
-------------------------------------------------------
-----Original Message-----
From: Steve Moffat [mailto:steve@xxxxxxxxxx]
Sent: Monday, October 31, 2005 12:42
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Blocking HTTPS
http://www.ISAserver.org
Then use https://www.google.com in the destination set also.
-----Original Message-----
From: mwarren@xxxxxxxxxx [mailto:mwarren@xxxxxxxxxx]
Sent: Monday, October 31, 2005 4:37 PM
To: ISA Mailing List
Subject: [isalist] RE: Blocking HTTPS
http://www.ISAserver.org
I tried what you said and this blocks the google site completely. We do
want to use some of the features that google provides. It is just the
mail (gmail) that we want blocked and it is a link on that page.
Blocking www.gmail.com blocks it, but it can also be accessed from
https://www.google.com.
MW
All mail to and from this domain is GFI-scanned.
Other related posts:
