> Another reason why apr_hash_t isn't a good match for HTTP headers > is that the same field name may appear multiple times in the request > or response headers (section 4.2 of RFC 2616), but the hash table > implementation is designed around unique keys.
HTTP headers were designed to be processed as a hash table, hence the rules regarding combining multiple fields with the same name. The only exception is Set-Cookie, because the folks at Netscape didn't follow the rules. ....Roy
