Apache HTTP Server
No written verdict yet. Here is what commenters said.
Why people recommend it
“When Apache became available we switched to it out of spite.”
Show 3 more
“The current setup has been running for 10 years now with minimal maintenance.”
“Apache was more than adequate for what I was doing, I had no issues with it in the past, and the setup was dead simple.”
“just an Apache install, the config for which I can automatically append new shortened links to”
Caveats and dissent
“but also loses the original response body.”
“It was so weird and I couldn't find it in the documentation”
Show 2 more
“Apache and NGINX busted pissed me off when creating simple ultra fast proxies, especially around web sockets”
Often compared with
Who recommends it in their own words
Threads where it came up
- The gap in shared understanding of LLM capability is widening 3 mentions
- Learn PHP in 2026 (Yes, Really) 2 mentions
- I Will Not Add Query Strings to Your URLs 2 mentions
- Chained PHP2Shell exploit roots 25 servers, including US Government servers 1 mention
- Show HN: Steal My Bitcoin 1 mention
- IRCv3 1 mention
Also written as Apache, Apache httpd. Data: apache-http-server.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 34
“Then similar for your web server (Apache, nginx, whatever).”
“Official WordPress docs mentions Apache before nginx”
“but also loses the original response body.”
“You can set up a server easily with Apache”
“It was so weird and I couldn't find it in the documentation”
“For Apache HTTP Server (what people mean by “Apache” in such a context), what you describe is thoroughly unbelievable.”
“When Apache became available we switched to it out of spite.”
“My stuff is all just Apache, PHP & SQLite”
“Apache and NGINX busted pissed me off when creating simple ultra fast proxies, especially around web sockets”
“before and after apache logs showing much less crap in them from bots”
it looks like it was built using the satire vibecoding components listed here yesterday https://vorpus.github.io/performativeUI/
“The current setup has been running for 10 years now with minimal maintenance.”
“Apache was more than adequate for what I was doing, I had no issues with it in the past, and the setup was dead simple.”
“my linux apache crashed when some one posted it here”
“Might want to read the section on Lingering Close”
“Apache still runs about 23-28% of websites”
“That's because Apache is basically what today's JS crowd would call a”
“This is because of a deeply annoying default in Apache”
“I abandoned it when they suddenly changed the configuration format.”
“setting the -Indexes option in the apache config”
“just an Apache install, the config for which I can automatically append new shortened links to”
“I've gone through this exercise on my own personal hobby nodes long ago.”
“just having an Apache2 config with some scripts to append to it”
“I never trusted .htaccess as it is by default dangerous”
“have it connect to port 80 on my Apache webservers”
“It works fine out of the box, for all my myriads of websites.”
“Apache and Nginx are both written in C.”
“I took a Django app that's behind an Apache server”
“the earliest httpd I could get my hands on is 1.3.0”
“nginx could handle 10x the requests of Apache httpd on the same hardware”
“perl-based cgis under Apache, running on my home server/workstation”
“Apache was prone to this”
“Apache lists some issues [1] with sendfile and defaults to off as well”
“I use both NGinx and Apache depending on what I am deploying”