Hello, Bernhard.

HTTP RFC define HTTP header field (HTTP options) semantics and meaning
of standart options.

So, according to RFC, there is a HTTP options and some specific subset
of options that have a predefined name and meaning. 

Therefore having all HTTP options in roundup-tracker (RT) internals
seems to be more standart complying than drop it all at begining of
request processing.

For example. If your Web sever reverse proxying to RT you may add to
HTTP options something like "X-Free-Registration: yes" according to
external condition. In current state you will never get this value
inside RT. I offer to have possibility to use it when needed.