The first step is to decide if you want to
generally allow HTTP on any port. If yes, and if
you use a proxy server that can be safely placed
in front of the firewall, move the proxy server
to the outside, allow only the proxy port through
the firewall to the proxy server, and the proxy
server can access HTTP on any port. If you are
filtering outbound connections on your router,
the router ACLs will have to be modified for this
to work, or your back where you started, do you
want to generally allow HTTP on any port?
---- Begin Original Message ----
From: "Network Operations"
<[EMAIL PROTECTED]>
Sent: Fri, 19 May 2000 09:41:23 -0700
To: <[EMAIL PROTECTED]>
Subject: What do you guys/gals think..?
Whats the general consensus?
Over the last few years more and more web
developers are redirecting web traffic to remote
servers with services running on various ports in
the 8000 range.
Following a strict deny-all-except policy, all
this traffic gets denied and logged. Consequently
my firewall logs have grown exponentially over
the last year, users are complaining that they
cannot get the information they need because "the
internet is down"...you know the drill..
Is there a trend here?
-
[To unsubscribe, send mail to
[EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the
message.]
---- End Original Message ----
Sign up today for your Free E-mail at: http://www.canoe.ca/CanoeMail
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
