Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
If you are referring to tokenization and and formatting of structured values of such headers, then MIME.tokenize and MIME.quote should be your friends. The detailed interpretation of the actual tokens would
The main problem is indeed the tokenisation. What is needed at various points is the decomposition of such a headerfield into an ordered structure which contains the key-value pairs.
Browsing through MIME, I find: MIME.decode_words_tokenized_labled(). It does some of the parsing, but the result it produces still takes considerable postprocessing in order to get to the key-value pairs we need. Maybe there is something better in there, which almost does what I need.
But it seems like the MIME library as-is has all the basic tools, but the tools still need to be integrated to get the key-value pairs.
Parsing headers from "lines" can be done with MIME.Message, which can also format them back into "lines",
MIME.Message would be way too heavy handed to parse merely a single headerfield.
but there is also Protocols.HTTP.Query.headers_encode for that. And of course if you are using Protocols.HTTP to make/process requests the module will take care of this for you.
The headers_encode creates the header-fields, but does nothing with the internal parameters per header-field. Then again, converting from structured data back to a valid header-field is easy and not the issue here.
I'll browse through the MIME libs some more to see if I can find salvation there. So far it seems a bit murky to me (for the use cases I described).