On Oct 27, 2:33 am, Michel Thadeu Sabchuk <[EMAIL PROTECTED]> wrote: > Hi again Simon, > > > @ Michel: I think the best approach is to use a separate IP for Lighttpd to > > listen on, but it should be equally easy to have Lighttpd listen on > > for example port 81. > > Hum, understood. The last one question (I think :-P). The use of > apache to redirect connections to lighttpd through mod_proxy isn´t > appropriated, is it? I want to do some action now and this is the > easiest way to act, so I can have some time to install a server with > apache worker, python with shared libraries and maybe mod_wsgi...
If you are already having issues with Apache's ability to serve up your static media files, using Apache as a proxy to lighttpd probably isn't going to make any difference as the content of the files still has to pass through Apache. It is possible that proxying via Apache for the static files may just make it a bit worse. If you want to proxy via one of the web servers, probably better to proxy via lighttpd, or as I suggested previously, have a look at Pound. Obviously better to use separate port/ip/machine for one media server. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
