Random headers lead to memory exaust.

[riktam]

Hi,
I'm using a web API in which the developers decided to add one randomly named header to every response.
Since the headers are interned in the keyword package, after a few hundreds thousand of calls both SBCL and CCL run out of (immobile) space where the symbols are stored.

Would you be willing to change the code to support strings instead of, or in parallel with symbols as header keys implementation?

[vindarel]

As a workaround, to my knowledge the other library doesn't have this issue (dexador).

[stassats]

A pull request that adds a variable controlling how the headers are parsed would be fine. Common headers should probably still remain as keywords.