Apache HTTP Server

57 engineers on Hacker News describe using Apache HTTP Server first-hand: 4 endorse it, 6 regret it, 3 are mixed.

43%trust
57first-hand users
52in production
endorse 4mixed 3regret 6uses, no opinion

“since Apache 2.4 came up with mod_proxy_fcgi, allowing dead simple integration with php-fpm.”

endorse · production · kijin · 2026-10-22 · source ↗ · wrong label?

“IMO you don't need to compensate for bad configs if you're using a proper staging environment... Apache lived in a container.”

mixed · production · rollcat · 2025-07-06 · source ↗ · wrong label?

“We switched from Apache to lighttpd back in the day specifically for performance issues”

regret · production · arp242 · 2023-05-20 · source ↗ · wrong label?

“It ran on Apache, and every time I upgraded MacOS, I had to fiddle with Apache config to get it working again.”

regret · personal · 15 yr · jdlshore · 2022-12-28 · source ↗ · wrong label?

“HTTPD has been my go to web server for years and I had used it so many times in production as a proxy/gateway. Always reliable.”

endorse · production · szastamasta · 2021-11-21 · source ↗ · wrong label?

“led the migration from Sun to Linux on the software side, switching everything to Apache was once a radical idea”

endorse · production · marcuskaz · 2021-01-09 · source ↗ · wrong label?

“I have been using Apache off and on since the late 90s. Other than development machines, I haven't seen an Apache site that wasn't load balanced.”

mixed · production · 15 yr · btilly · 2014-11-17 · source ↗ · wrong label?

“we saw some 50 instances of Apache and each taking 25 Mb memory.”

regret · production · rehack · 2013-09-07 · source ↗ · wrong label?

“Apache had been good to us in the past, despite being the 1.3 series with patches bundled with OpenBSD, but we were expecting far more from it”

mixed · production · eksith · 2013-09-06 · source ↗ · wrong label?

“I have seen Apache ignore updated PHP files, and serving old code, which should never happen. This a real bitch to debug.”

regret · production · rorrr · 2011-11-18 · source ↗ · wrong label?

“migrating to Apache worker MPM has enabled me to handle loads on the same hardware”

endorse · production · unoti · 2010-12-22 · source ↗ · wrong label?

“tried to switch apache to port 81 to be able to configure the cache plugin. But even this way, all the disk accesses were taking 30 seconds each...”

regret · personal · sylvinus · 2010-12-10 · source ↗ · wrong label?

“I haven't used apache httpd in production for years and I'm happier for it. It's inefficient. .htaccess only compounds that inefficiency.”

regret · production · runningdogx · 2010-11-07 · source ↗ · wrong label?

“When Apache became available we switched to it out of spite.”

neutral · production · Suzuran · 2026-09-15 · source ↗ · wrong label?

“throw a CGI script behind an Apache HTTP server, which tended to be up and running”

neutral · production · ojosilva · 2025-11-19 · source ↗ · wrong label?

“Back in the earlier days of web hosting we'd run into this with Apache.”

neutral · production · geocrasher · 2025-06-06 · source ↗ · wrong label?

“All based on Apache, IIS and Tcl.”

neutral · production · pjmlp · 2024-12-25 · source ↗ · wrong label?

“We run NewRelic configured to monitor Apache”

neutral · production · rawleyfowler · 2023-11-04 · source ↗ · wrong label?

“we are running our personal websites on apache and also hosting our DNS (bind) and email (postfix)”

neutral · personal · igor47 · 2023-08-17 · source ↗ · wrong label?

“The part I enjoyed the most was automating Apache and systems administration work for the server farm”

neutral · production · l8nite · 2022-11-20 · source ↗ · wrong label?

“sometimes Apache would just drop the connection”

neutral · production · baryphonic · 2022-08-03 · source ↗ · wrong label?

“I am used to creating "web application" and running it on a web server of some sort: Apache / IIS /Lite.”

neutral · production · ThinkBeat · 2021-12-05 · source ↗ · wrong label?

“using Tcl as Apache/IIS plugin in our own AOLServer inspired application server”

neutral · production · pjmlp · 2020-12-25 · source ↗ · wrong label?

“we have an "apache2ctl configtest" when a cert is renewed to verify that Apache (or equivalent) can read the files correctly”

neutral · production · throw0101a · 2020-09-10 · source ↗ · wrong label?

“an in-house application server written in a mix of Apache plugins and Tcl”

neutral · production · pjmlp · 2020-07-09 · source ↗ · wrong label?

“we were a big Perl Apache and MySQL shop.”

neutral · production · mmaunder · 2019-10-22 · source ↗ · wrong label?

“mod_perl 1.4 on Apache 2.0 handling 350,000 hps dynamic traffic on twenty archaic 1U's.”

neutral · production · peterwwillis · 2018-11-14 · source ↗ · wrong label?

“This Apache plugin not only requires Apache, but it has to sit on top of a properly configured Fuse file system.”

neutral · production · bmurphy1976 · 2018-07-10 · source ↗ · wrong label?

“launches all services required (e.g. apache, mysql, sshd, elasticsearch) by running "service XYZ start"”

neutral · production · mschuster91 · 2017-10-27 · source ↗ · wrong label?

“Drop a few php files under Apache and keep marching forward.”

neutral · personal · borplk · 2016-10-11 · source ↗ · wrong label?

“it decides to completely fuck up your apache webserver config and you have to spend a whole day to properly configure your virtual hosts again.”

neutral · personal · kuschku · 2016-06-05 · source ↗ · wrong label?

“We run LAMP (Linux-Apache-MySQL-PHP) stacks on virtual machine instances on servers worldwide of our choosing.”

neutral · production · kaa2102 · 2015-10-04 · source ↗ · wrong label?

“Our apache was 2.2.29, it is recommended for 2.2.31 due to the 1 CVE.”

neutral · production · mediacatch · 2015-07-29 · source ↗ · wrong label?

“Ruby, PHP, NodeJS, Apache...it's all there.”

neutral · production · bluedino · 2015-07-02 · source ↗ · wrong label?

“still fairly heavily tied to Apache2/mod_perl and other parts of our internal libs”

neutral · production · robn_fastmail · 2014-12-20 · source ↗ · wrong label?

“we use LAPP (PHP, Postgres) with Laravel, Backbone - also with Redis for caching.”

neutral · production · sideproject · 2014-12-05 · source ↗ · wrong label?

“Then you pick it up in the Apache conf file.”

neutral · production · sideproject · 2014-12-03 · source ↗ · wrong label?

“mod_perl is pretty fast in itself (using Apache).”

neutral · production · arc_of_descent · 2013-12-19 · source ↗ · wrong label?

“We use linux for: redis, elasticsearch, HAProxy, DNS (bind), nginx, mail (exim) apache, wordpress, mysql, nexpose, backups, puppet, asterix, android builds and our internal mercurial.”

neutral · production · Nick-Craver · 2013-10-16 · source ↗ · wrong label?

“I use apache, so I have to figure that out as well.”

neutral · production · andmarios · 2013-10-05 · source ↗ · wrong label?

“We use Apache as a frontend because we are an hosting company and customers want .htaccess”

neutral · production · rdeioris · 2013-06-28 · source ↗ · wrong label?

“put Apache with mod_auth_form in front of it (or ISA server)”

neutral · production · y0ghur7_xxx · 2012-11-07 · source ↗ · wrong label?

“we run Node right on our existing Apache Web servers (behind haproxy).”

neutral · production · blantonl · 2012-05-17 · source ↗ · wrong label?

“run a custom-built Apache in production (no patches, but highly-tuned build configuration)”

neutral · production · cwp · 2011-12-29 · source ↗ · wrong label?

“As of now, we have a simple script going thru apache logs”

neutral · production · tlogan · 2011-11-04 · source ↗ · wrong label?

“I don't need to change python/apache etc. that often, it is not like I need to recompile for every code deploy.”

neutral · production · tingletech · 2011-09-15 · source ↗ · wrong label?

“Set MaxClients to 8.”

neutral · production · wheels · 2011-07-14 · source ↗ · wrong label?

“we run a very straight forward Rails hosting stack (Apache/Passenger/MySQL)”

neutral · production · bradleyland · 2011-06-22 · source ↗ · wrong label?

“I don't even think I've bounced any services like apache or passenger on that box in over a year.”

neutral · production · rapind · 2011-06-15 · source ↗ · wrong label?

“We are considering switching from apache, but the current setup works so well that we don't want to mess with it”

neutral · production · StavrosK · 2010-10-25 · source ↗ · wrong label?

“We bypass Apache entirely and just plug Nginx FCGI into Django directly.”

neutral · production · adamcharnock · 2010-10-23 · source ↗ · wrong label?

“On top of those, we use Apache, mod_wsgi, Fabric (in a slightly-weird way which I'll get into below), mod_xsendfile, Mercurial”

neutral · production · rcoder · 2010-10-23 · source ↗ · wrong label?

“We use PHP and Apache, so the gloating about ASP being way more efficient than PHP seems to be unfounded.”

neutral · production · wanderr · 2010-10-14 · source ↗ · wrong label?

“We use PHP and Apache, so the gloating about ASP being way more efficient than PHP seems to be unfounded.”

neutral · production · wanderr · 2010-10-14 · source ↗ · wrong label?

“We switched from Apache to nginx and are now running in a full MySQL / python / fcgi / nginx / memcached environment.”

neutral · production · omarish · 2010-06-29 · source ↗ · wrong label?

“it would hang Apache and/or just start returning 500 errors until the web server was restarted.”

neutral · production · mattw · 2010-05-19 · source ↗ · wrong label?

“Apache webservers with nginx front-ends”

neutral · production · scorchin · 2010-02-05 · source ↗ · wrong label?