Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> And yet we have only a handful

Apache, nginx, haproxy, envoy, traefik, and probably dozens more that aren't on the top of my head.



You literally listed a handful ;)


Fabio, IIS, Varnish, Kong, Squid, lighttpd, emacs (probably).



Actually Emacs as a dev proxy like Charles Proxy could be handy... ;)

Also there exists an http module for emacs: https://www.emacswiki.org/emacs/HttpServer


> > > And yet we have only a handful

> > Apache, nginx, haproxy, envoy, traefik, and probably dozens more that aren't on the top of my head.

> You literally listed a handful ;)

How many solutions to a problem are needed when the problem is well-defined before there is no longer a need to grab for more?


There are probably thousands on Github for the use of teeth-cutting like in the blogpost. I've made one. You just lose interest when you impl the easy/naive stuff and need to actually use a real solution in production.


[flagged]


Apache's httpd is perfectly good as a web server, and passable as a proxy. I can't say that it'd be my first choice, but I'm not aware that there's any special reason not to use it.


The Byzantine config file syntax was a common complaint shared by the early defectors to nginx. If I never have to edit that conf file again it will be too soon.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: