[RFC] "http-types" breakage / additions / rework

viktor:

While an application that is strictly conformant with the HTTP specifications must abide by the rules, the same is not necessarily true when parsing response headers from a less meticulously implemented peer.

Which means there are two different concepts here:

• List of raw headers as provided in the HTTP request;

• Library-augmented set of headers served to the user at the high level.

Should the latter be in http-types, wai or somewhere else? Couldn’t tell you.

Vlix:

There’s a bunch of type synonyms instead of newtypes, and all of the data constructors and fields of data types are exported.

I wouldn’t be surprised if http-types is the only package using case-insensitive, everyone downstream is forced to include it just to work with header names.