I have a web server inside of my company that people outside
the company need access to. For several reasons it is not a good
idea to put the machine directly in the firewall. There are also
good reasons not to put it outside the firewall and replicate the
internal machine to it. And I'm not inclined to pass the requests
I was wondering if I could use a cache server like Harvest to do
this. The html is generated on the fly from a database depending
on who accesses the page. Is using a cache server for this a
reasonable approach? Has anyone had a similar problem or done this
Any input will be greatly appreciated.
Welcome to the firewalls-digest mailing list!
Please save this message for future reference. Thank you.
If you ever want to remove yourself from this mailing list,
you can send mail to <Majordomo @
COM> with the following
command in the body of your email message:
unsubscribe firewalls-digest jhammond @
Here's the general information for the list you've subscribed to,
in case you don't already have it:
This list is for discussions of Internet "firewall" security systems and
related issues. It is an outgrowth of the Firewalls BOF session at the
Third UNIX Security Symposium in Baltimore on September 15, 1992.
This is the digestified version of the list. Digests are sent daily
(assuming there were any messages to the list that day) or whenever
the current digest grows beyond 40k bytes. The undigestified version of
the list is "Firewalls @
COM". To subscribe to Firewalls, send
"subscribe firewalls" in the body of a message (not on the "Subject:" line)
to "Majordomo @
Frequently Asked Questions
A "Frequently Asked Questions" (FAQ) document (written by Marcus Ranum,
com) is available via anonymous FTP from host FTP.GreatCircle.COM,
file pub/firewalls/FAQ, or from Majordomo by sending the command "get
firewalls FAQ" in the body of an email message (not on the "Subject:"
line) to address "Majordomo @
COM", or via URL
Code for cracking programs (programs designed to help break into another
system) should not be posted to the Firewalls mailing list.
You can subscribe a local redistribution list or a gateway to a local
newsgroup, as long as whatever you do is local to your site. This
restriction makes it much easier for me to track down mailer problems.
I'm very aggressive when it comes to bounced email. If email to you
starts bouncing, I'll probably drop you from the list fairly quickly;
you'll have to resubscribe when you get the problem fixed, and retrieve
the archives to find out what you missed.
All digests are archived. The archives are available via Majordomo using
the "get" command (send "help" in the body of a message to
COM" for more info), or via anonymous FTP from
host FTP.GreatCircle.COM in directory "pub/firewalls/digest", or via URL
The digests are broken down by volume and number, and are stored in files
named "vNN.nMMM", where "NN" is the volume number, and "MMM" is the issue
number. The copy of the digests available by anonymous FTP is updated every
night at 2am local time (0900 GMT in the summer, 1000 GMT in the winter).
The Firewalls-Digest archive is available by WAIS on host WAIS.GreatCircle.COM,
at port 210, under the database name "firewalls-digest". The WAIS archive
is updated nightly.
The FAQ document is also avialable by WAIS on host WAIS.GreatCircle.COM,
at port 210, under thedatabase name "firewalls-faq".
For Further Information
Michael C. Berch
Postmaster and list manager, Great Circle Associates