Hi Thomas,

A typical setup for your environment would be to set an apache  reverse proxy 
in front and
handle the dynamic content on a dedicated backend server. You can put your 
static
files on your reverse proxy or serve them via another backend server.
The important part is to split dynamic and static content, just like you intend 
to do.

Putting all static content on the same physical machine, but on a different 
Apache
running on a different port sounds like a lousy setup to me. Consider clients
trying to access your service but their firewall blocks outgoing requests to 
anything
but port 80 and 443.

regs,

Christian

-----Ursprüngliche Nachricht-----
Von: thomas Armstrong [mailto:[EMAIL PROTECTED] 
Gesendet: Montag, 31. März 2008 12:46
An: users@httpd.apache.org
Betreff: Re: [EMAIL PROTECTED] Apache 2.2 as a static server (without PHP) to 
serve images


>  Sure, make a copy of the httpd.conf file, remove everything that 
> refers  PHP (the LoadModule basically), then run a secondary Apache 
> using that  config file. You'll have to use a different port of course 
> and redirect  images and the like to the secondary apache.
>
>  But... why?

Thank you very much for your answer.

AFAIK, when Apache answers a petition of dynamic content, it requires 10-20 MB. 
If you request for an image, then this 20MB process is serving static content 
inefficiently,  which could be served just by a 1MB process.

So I want to run another Apache with less memory requirements to serve these 
static contents.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to