How do I configure Lighttpd to serve images/javascript/css files that are littered about my websites? Can I just input the paths of all the directories that I want Lighttpd to serve from?
For example, I have 4 separate websites with each having a message board, main page etc... Could I have lighty serve the files from:
My server is Win2003 Standard with IIS 6. I'm using IIS6 to host websites but i have a need to run subversion which require Apache. I'm wondering would it cause any problem with my current operation. Apache will run on different port than the standard 80.
I'm not sure if this is the right forum, or if anyone can suggest a message board where I might get support on this.
This is what I have. I have Apache and IIS both running on Windows 2k3.
Apache is running in reverse Proxy mode sending multiple domains/virtual hosts to IIS.
Code:
ProxyRequests Off <VirtualHost *:80> ProxyPreserveHost On ProxyPass / http://localhost:8080 ProxyPassReverse / [url] ServerName mydomain.com
</VirtualHost> Now, if I type in [url]everything works great and IIS (listening on 127.0.0.1:8080) serves the page. However, I am doing custom error trapping, so when I type in [url](and /mydirectory doesn't exist on IIS) I need to fire ASP code (via custom error messages/handling) on the IIS server and then present a data driven page.
However, Apache is returning A 502 error:
Code: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /mydirectory.
Reason: DNS lookup failure for: localhost:8080mydirectory Is there a way for me to setup Apache to pass all error checking to IIS while using it as a reverse proxy?
my php.ini had some changes (/etc/php.ini). Today i have switch from apache to lighttpd, do i need to edit another php.ini file ? Apache and lighttpd use the same php.ini ( /etc/php.ini)?
Until recently, it seemed like everything I read about a server indicated that Apache was king. I have never read anything that has given me any reason not to use Apache.
However, about a year ago when I discovered Django, I discovered Lighttpd. From everything I've been able to read, Lighttpd seems to be a better web server, but still don't know very much at all about Lighttpd.
I'm fairly comfortable with Apache, although I've never cared much for it. I have a feeling that I'll like Lighttpd quite a bit more from the very little that I do know about it. I'm wondering if I should even consider switching.
For one, it seems that everyone knows how to work with Apache and Lighttpd seems to be far less common. Apache also seems to be much more established which leads me to believe that it's a safer choice. Nonetheless, I still really want to give Lighttpd a shot. And, judging from what I've seen about Django and Lighttpd, Lighttpd seems to be a better choice when working with Django.
What do you think? Should I stick with Apache since I already know how to use it? Is Lighttpd worth the time to learn or is Apache just too good?
I wanted to know what do you prefer as server apache or lighttpd , though I am running lighttpd and have no issue except that there is too much work for mod rewrite and it effects search engine, so I was thinking to use apache instaed of it will it be possible to install apache over lighttpd or will I have to go for fresh install.
For a year now I've been running my server with Lighttpd. It's worked out well so far, but now that I have a new box I'm reconsidering.
Lighttpd does not support .htaccess files which is a bit of a pain, and doesn't have the same support by apps like Apache does. Given that I get very little traffic to my box (it sits idle most of the time) I am considering Apache.
How is security between Apache and Lighttpd? I know Apache has things like mod_security and mod_evasive, but I've never really checked how Lighttpd compared.
We've been thinking about writing our own hosting control panel for our own "tight" hosting setup, so that can alter the panel just to our needs without relying on updates from anybody else.
To read new configurations in Lighttpd or Apache, as far as I know, requires the software to be restarted (for example service apache restart). Are there any negative effects of this, I'm assuming that whilst being restarted there is a small amount of time during which the software is "down" and websites can't be accessed during that period (probably <1 second). Am I correct?
What is the best way to reload configurations into these http servers without service interruption? I notice that DirectAdmin seems to just restart Apache on any function that alters the configuration file - for example adding a new user.
index-file.names = ( "index.php", "index.html", "index.htm", "default.htm" ) and my httpd.conf
Code: ProxyRequests Off ProxyPreserveHost On ProxyPass /lighttpd http://0.0.0.0:81/ ProxyPassReverse / http://0.0.0.0:81/ Now when I created a folder on my server's httpdocs /lighttpd/
everything runs smooth so I got the lighty to work for me.
Okay now that i figure it works I wanted to run one of my subdomain on lighty so that I can reduce the load on the server. Does anyone know how I can setup one of my subdomain to open with lighttpd and keep everything else on apache?
Has anyone done this or currently running this setup? to try it with my directadmin server first but havent found very good documentation or howtos. Ive looked the last week or so and havent really found anything helpful. So if anyone is running such a setup Id like to know how you did it and how much better if any it is.
I'm running both Apache (on port 81) and Lighttpd (port 80) on my VPS. I would like to have Apache run CGI/Perl scripts only for virtual hosts in the Lighttpd.conf. My Lighttpd.conf already has fastCGI enabled though.
There are 2 different domains with the same IP being served by Apache. I want one of the domains to be served by lighttpd, is it possible without having to change the IP of that domain?
somebody know is possible on some way route traffic before come to web server (apache or lighttpd)?
I want to setup lighttpd on port 80 and apache on port 81 and I want visitors to go direct to apache or lighttpd without url:81 and that must work on this way if somebody visiting url1.domain.com that go to lighttpd on port 80 and if somebody visiting url2.domain.com that go to apache on port 81 and something must route it before lighttpd and apache (and get/post must work), is this possible on some way?
I know that lighttpd and apache can do it but I don`t need it on that way!
I've installed apache on my windows 2008 vps . It's run and when I browse localhost , it's works fine . But when I enter the vps ip address , it says Chrome could not connect to ... , I'm sure that httpd is running on port 80 (I checked it via netstat -ao and task manage ) ....
I'm not an admin, I can't make apache run cgi's, I have followed several documents in different pages without luck, I can run normal html pages but not cgi's. I only get the code displayed in screen.
I have small issue with load speed of pages when number of apache running processes goes over +-310, during peak traffic of day. IE: They load really slow.
Here's pic of what I mean:
=> [url]
Only thing that fixes it temporarily (at least until peak traffic ends) is to stop either httpd or mysql for several seconds, as everything cools down, then start it back up. Stop/starting mysql usually has longer terms temporary fix.
Anyway, would you have any ideas on what to configure or change within the system in order to keep the processes under 300?
The load is normal. Even at load 40, pages are blistering fast, as long as processes are under 300. So it's got nothing to do with load.
My server was running a cronjob backup, and my apache always fail
root@b# service httpd restart /etc/init.d/httpd restart: httpd not running, trying to start /etc/init.d/httpd restart: httpd started root@b# service httpd restart /etc/init.d/httpd restart: httpd not running, trying to start /etc/init.d/httpd restart: httpd started root@b# service httpd restart /etc/init.d/httpd restart: httpd not running, trying to start /etc/init.d/httpd restart: httpd started
I can only restart them on my CPanel WHM
Attempting to restart httpd Waiting for httpd to restart.... . . . . . . . . . . finished.
httpd status root 5805 0.8 0.9 21092 19504 ? S 22:39 0:00 /usr/local/cpanel/whostmgr/bin/whostmgr ./reshttpd root 1012 4.0 0.6 23348 13828 ? Ss 22:39 0:00 /usr/local/apache/bin/httpd -DSSL
httpd started ok
root@b# service httpd restart /etc/init.d/httpd restart: httpd restarted
Code: [root@serwer /]# httpd restart /usr/sbin/httpd restart: httpd not running, trying to start /usr/sbin/httpd restart: httpd could not be started
Code: [root@serwer /]# httpd status Looking up localhost Making HTTP connection to localhost Alert!: Unable to connect to remote host. lynx: Can't access startfile [url]
We run httpd-2.2.3 on CentOS 5.8 with caching enable. The server has been running for 4 years, but htcacheclean has never been run. The cache folder is about 10GB now (a "du" on the folder takes a very long time to complete). Should we expect any problem when running htcacheclean for a first time such as server slowing or freezing, ... Furthermore, in case of freezing, if we disable caching and restart the server, do we expect any problems? We did a few test on our test servers, and everything was fine, but our test servers do not have a large cache folder.
I have been a web developer using PHP for years now, and my work laptop runs CentOS with PHP5 as an Apache Module. This suits me just fine for development, but now I want to setup a web server that runs PHP 4.4.8 and PHP 5.2.5 and offer hosting to people. I know PHP4 is very old, but I am looking to offer my users the freedom of choice, as there are still third party applications out there that may need to be run on PHP4.
I will want PHP 5 to be the default, and allow PHP 4 to be used if either the file extension is .php4, or they have a line in their .htaccess file. I have seen various tutorials in search engine results saying to run both, I can either do one of the following:
1. Install PHP5 as a module, and run PHP4 using FastCGI 2. Install PHP5 and PHP4 and run both using FastCGI 3. Install PHP4 as a module, and run PHP5 using FastCGI
In the future I will also be looking to support PHP6 once a stable version has been released, though that will probably be optional to begin with and require a line in the .htaccess file too - like PHP4. I will be using Apache 2.2.8 on CentOS 5.1. I am also looking to install Ruby on Rails and Django too, which I think use FastCGI.
What's the difference between running as an Apache Module, or using FastCGI? This will be for a shared hosting environment so performance over lots of connections, stability and security are my concerns. Should I run everything using FastCGI, if not, would the default PHP version be better off installed as an Apache Module?
I am trying to run a simple script which brings up a gnome terminal on the user's display. I have created a perl cgi script which calls a shell script using a system call. If I run the perl cgi script from the command line, it brings up the gnome terminal correctly. If I try running the perl cgi script via the Apache web server, I get the following error in /var/log/httpd/error_log:
