-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M3u add parsing of forwarded header wip #716
base: next
Are you sure you want to change the base?
Conversation
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 |
f346f45
to
6ee70b1
Compare
First step: rebased and whitespace and imports cleaned up. |
0d4814d
to
92c4424
Compare
Second step: more cleanup and some force pushing, because it should now be much easier to check. |
eecfda3
to
cbfac8a
Compare
cbfac8a
to
6d51184
Compare
@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 |
only merge after m3u is merged!
WIP, because parsing that header directly needs somewhat careful checking.