Unlike Apache, I believe we should design the serf to pass the HTTP headers through the filter chains. Apache couldn't really do it because of backwards compat issues (the presence of r->headers_in and r->headers_out).
But we're starting fresh. Adding a header bucket will allow filters to examine the request/response headers to control their function and to manipulate the headers. I believe a header bucket is simply an apr_hash_t of headers. Adding and looking up headers requires a bit of extra glue to lower-case the header name. Using a hash means it is very easy to set aside the headers (waiting for the end-of-header bucket so a header can analyze the full set of hdrs), manipulate them, and to gather them up (we need to add a "merge" function to the hash table, although merging headers requires a bit more than simple overlap). Cheers, -g -- Greg Stein, http://www.lyra.org/
