←back to thread

154 points feep | 1 comments | | HN request time: 0.201s | source
Show context
sugarpimpdorsey ◴[] No.44464798[source]
Surprised with the choice of Apache. There are better choices for serving CGI nowadays. The only reason for still running Apache is you have legacy cruft that requires Apache (like .htaccess).
replies(5): >>44464841 #>>44464842 #>>44465210 #>>44466147 #>>44469039 #
1. Twirrim ◴[] No.44465210[source]
Apache's httpd is great, reliable, fast, and feature-full, and you don't have to deal with Nginx's ongoing conflict over the the open source vs commercial offerings. That conflict has caused needless pain, like e.g. that quirk around dns resolution where if you put the hostname under proxy_pass it only used to resolve it on start-up and ignored TTL (not sure if it's still doing that). There were work-arounds on the open source version, like using a variable instead, but that wasn't necessary in the commercial offering.