M3u add parsing of forwarded header wip
only merge after m3u is merged!
WIP, because parsing that header directly needs somewhat careful checking.
only merge after m3u is merged!
I guess this could now use a merge or a rebase, whichever you prefer. :)
Please don't mix formatting changes with code changes... it makes reviewing PRs such as this one very difficult
First step: rebased and whitespace and imports cleaned up.
Second step: more cleanup and some force pushing, because it should now be much easier to check.
@Bombe I added tests and fixed the case sensitivity (keys must be insensitive). But this isn’t tested in production, yet.
Hmm, according to RFC 7239 there can be multiple Forwarded headers in a request but I can’t spot any handling of that…
@Bombe @ArneBab some news about his PR ? still relevant ?