Hacker News Reader

Comment by detaro | Hacker News Reader

Supports TLS using LibreSSL, serves static files and FastCGI.

https://github.com/reyk/httpd/issues?q=label%3Afeaturitis+is...

featuritis tag in die bugtracker for currently denied features. Clearly aiming for as simple as possible while being useful.

View on HN

In one of the comments on the "featuritis" tagged issues:

> I add the label "featuritis" to remind us of extra features (eg. ldap) that we reject now but might want to reinspect later.

So it's not that httpd will never be extended beyond the basics, but these issues are simply out of scope right now. I like that approach.

What is wrong with compressing static files?

That's a good question. Though a better question might be "why not serve pre-compressed static files alongside regular files?"

Compression will change your server from being network throttled to being CPU throttled. And in this day and age, we can scale CPUs more easily than we can bandwidth.

Pre-compressing is possible, but why shouldn't the http server do it for you? The server can cache the compressed files in memory and/or disk as it sees fit (although gzip was pretty cheap last time I checked). It can also deal with cache invalidation better than humans - I speak from experience :).

Very true. The difference lay in the benefit of not having to implement the compression logic as part of the server, making the server implementation much simpler.

And it's funny, Windows/IIS makes you install dynamic compression separately, in the name of security. (Course, they also make you install the tftp client separately, under the same "reasoning".)

More information: http://bsd.plumbing/about.html

Reply on news.ycombinator.com