Re: A fnord fork (a fnork?)

Felix von Leitner <[email protected]> Thu, 16 Feb 2012 23:54:52 +0100
Newsgroups gmane.comp.web.fnord
Message-ID <[email protected]>
> I'm using fnord for my Capture The Flag contest
> (http://dirtbags.net/ctf/) and have been maintaining a forked version
> under git (http://woozle.org/~neale/gitweb.cgi?p=fnord).  Last week I
> began seriously overhauling the code to better suit my needs.  Here's
> the changelog so far:

>   Add all patches from (defunct) Debian package

Don't know about those.

>   Replace libowfat with libc
>   Replace buffer_1 and buffer_2 with stdio

I'll certainly not pull those changes in.

>   Fix segfault with directory listing of /

Wait, what?

>   Replace compile-time options with command-line ones

I'll also not pull those changes in.

Code you don't have in the binary can't have bugs and can't be
accidentally activated.

>   Add regression test suite
>   Fix if-modified-since date parsing

What's wrong with it?

>   Make text content-types use charset=UTF-8

I would actually consider it a bug if you do that.

>   Change default content-type to application/octet-stream

gatling does that, too.
I'm not sure which one is better.
That's a religious question, I think.  A case could be made for
configuring this on the command line.

>   Makefile no longer overrides CC and CPP from parent makes

What parent makes?
If you want to integrate fnord into some larger build system, then ...
well integrate it.  That's why it's called integration.  Because you
might have to touch it.

>   Don't send Content-type if there's no content

Why?

> I'm currently working on a problem with CGI end-of-header parsing that I
> discovered with the regression test suite on different platforms.

Please elaborate?

> It occurs to me that:

> 1. Other people might be interested in this, and
> 2. It's diverged to the point that I should either rename it or claim
> maintainership

> This list seemed like the best place to find out about both points.  I'm
> particularly interested in how Felix feels about point 2.  The removal
> of libowfat seems like a big enough departure that he might prefer a
> fork, but who knows!

Fork away if you want to, but if you actually discovered bugs, then I
would like to hear about them.

I don't get why you would want to remove libowfat, to be honest.  That
and dietlibc are what makes fnord viable as a web server in practice.
Because the static binary is so tiny.

Felix