Eric:
I am not familiar with pound...
My reverse proxy is only for web requests :)
I want "http://<domain>/perl/*" to be proxied; I don't mind if my lightweight apache handles stuff like "http://<domain>/imgs/logo.png"
That way my memory intensive perl app doesn't consume large amounts of memory for requests of static content (the lightweight non-apache server takes care of that)
If each perl enabled apache process consumes 5 megas (depends on the app) 100 processes consumes 500 MB. I can cut the memory usage down by making my apache processes more specialized. Vanilla apache for requests that do not require perl and all it memory baggage, and Perl apache for those requests that are dependent on some perl processing.
I can have 50 or 100 lightweight apache processes running and 5 or 10 perl enabled apache processes without paying for the memory of 100 perl processes.
I am not sure if pound fits my requirements
Leo
Eric S. Johansson wrote:
Leo wrote:
Is there a preferred *Gentoo* way setup this up?
Any suggestions, pitfalls alerts, or comments are welcome.
yea, use pound.
the Apache reverse proxy has some nasty pitfalls which can leave you open to attack by spammers. i.e. they use your proxy to connect to other mail servers. while you can close the holes, the question should be why work so hard? Pound fails safe unlike Apache which fails open. You can even use xforward options to make your logs more accurate on the Apache side.
---eric
-- gentoo-user@gentoo.org mailing list
