Bozohttpd

Conflicts:

- main.c
- content-bozo.c Leaf check-in: c9541b58b7 user: atomicules tags: trunk

When I merged in upstream I missed the colon after `h` which means the program
segfaults as soon as I try to set a Cache Control header. This was a bit dumb
of me since I knew about this here:

https://fossil.atomicules.co.uk/bozohttpd/info/a29fb4fb10ecaeea

But it was a messy merge. check-in: 00fe7ad50c user: atomicules tags: trunk

This is mostly due to blacklist being renamed to blocklist _somewhere_ (NetBSD
Current? I thought 9.2, but nope). I.e. it's harmless to have `-lblocklist`
_if_ that library actually exists even if we aren't compiling that in. But that
also seems wrong. So let's check the compile options and remove that linker if
we aren't compiling blocklist support in. check-in: 1eccc4f90c user: atomicules tags: trunk

Ideally I'd prefer to do it with a regex or partial match on the content type, but everything is already setup for us to piggyback on this instead. I.e. I'd like to do multiple arguments like this:

-h "image" "private, max-age=604800" -h "css" "private, max-age=86400"

or a single argument where we split the string on a comma:

-h "image,css" "private, max-age=604800"

but instead I am happy enough to be able to do:

-h .jpg "private, max-age=604800" -h .png "private, max-age=86400"

It's good enough for what I want to stop here.

- Adds a new cache-bozo.c file
- Adds a new field in the existing map used for the cache control header
- Extends all existing functions as required to reference this new field. check-in: 6d39f799f6 user: atomicules tags: trunk

A bit of an intermediate commit, just investigating what works. I think really
need to be able to pass in a string and a cache-control header and it'll use
strstr to determine which header to set. I.e so you can pass in:

"image" "max-age=604800"
"css" "max-age=86400"

The bit I'm then missing is how to set a catch all or "owtelse" cache-control?
Maybe look for one argument? check-in: dda2552f49 user: atomicules tags: trunk

The bit that foxed me was understanding getopts and that the "h" needed a ":"
after it because the option accepts and argument. It'll happily build and run
without this, but segfault when you try to use a "-h" argument.

This definitely and utterly sets a header. It doesn't seem that it's recognised
properly for whatever reason though, e.g here:

- https://developers.google.com/speed/pagespeed/insights/

and here:

- http://highloadtools.com/cachecontrol

But what can you do?

At the moment this just sets a header everywhere for everything being served.
What would be better would be just setting this on certain file types. check-in: a29fb4fb10 user: atomicules tags: trunk