Would Apache fit in with this situation or is it intended as (in our case) an Intranet server?
I am not quite sure what you mean by 'fit in' - if you mean will it run on the same box - yes. If you mean will act as an internet web server too - then see http://www.netcraft.com/survey/ - apache runs 60 % (and growing) of the worlds web servers ;-) If you mean will it do the proxy/caching stuff - then it could do, but I think (from what I hear - I don't actually know myself) that squid would be better ... (on shaky ground now ...) If you want apache to run just internally, then it is worth bearing in mind that any box actually connected to the internet and doing internet things (DNS, mail, etc) should really only be running with the minimum features enabled to do its job, in the interests of security. So I would recommend running apache for internal purposes, (if that is what you want), on a separate machine ... Just my opinion Kevin.
If you mean will it do the proxy/caching stuff - then it could do, but I think (from what I hear - I don't actually know myself) that squid would be better ... (on shaky ground now ...)
Apache will do the proxying fine, as well as the intranet, and it can serve the intranet externally as well if you wish. Squid will do the proxying fine too, well, finer, it's a better proxy, more control, but it's also more complex to tune. For a small system use Apache for both.
So I would recommend running apache for internal purposes, (if that is what you want), on a separate machine ...
If you do run it on a separate system you have more problems configuring personal cgi scripts and other exciting things, whereas if run on your main system you have direct access to all the data you want, much more fun, and still very difficult for hackers. Run Squid on a separate machie: Squid takes quite a bit of memory. -- Christopher Dawkins, Felsted School, Dunmow, Essex CM6 3JG 01371-820527 or 07798 636725 cchd@felsted.essex.sch.uk
participants (2)
-
Christopher Dawkins -
kevin.taylor＠powerconv.alstom.com