ignore content-type encoding when choosing a parser for topic data
authorJustin Wind <justin.wind+git@gmail.com>
Tue, 10 Aug 2021 21:25:42 +0000 (14:25 -0700)
committerJustin Wind <justin.wind+git@gmail.com>
Tue, 10 Aug 2021 21:25:42 +0000 (14:25 -0700)
Now it will properly strip any encoding from content-type header before
comparing against available parsers.


No differences found