Make header reading compliant with RFC7230, section 3.2.2

[Croug]

RFC7230, section 3.2.2 specifies that headers can be joined by comma separating the values so a header like this Authorization: Bearer <JWT>, Basic <B64EncodedCreds> is valid

[pep8speaks]

Hello @Croug! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2019-09-10 21:01:57 UTC

[vimalloc]

I had no idea that was valid, thanks for the pull request! If you don't mind, could you throw a quick unit test around this this? Then I will get it merged and a new release cut ASAP.

Thanks!

[Croug]

Yeah no problem, I will get them set up tonight.

[coveralls]

Coverage remained the same at 100.0% when pulling cd33d54 on Croug:master into 391de47 on vimalloc:master.

[Croug]

I've added the unit tests

[Croug]

@vimalloc

[vimalloc]

A couple minor things, if you could get those changed and fix the pep8 errors (#270 (comment)) I think this should be good to go.

Thanks for contributing!

[vimalloc]

Sorry for the delay in getting back to you, I was not around this weekend. I left a couple comments, if you can update those I think this looks great and I could get a new release cut.

Thanks!

[Croug]

Alright, finally managed to fix all the pep8 issues, my editor was exhibiting some weird behavior that kept creating new issues, but it should all be good now, I also fixed the ambiguity call when multiple header fields have the same value and reverted the config change

[vimalloc]

Thanks! I'll get a new release cut stat.

[vimalloc]

Released as version 3.23.0. Thanks for contributing! 👍