Describe the bug

The current implementation of the authorization header parsing has (at least) the following issues:

• A value can't contain any commas
• A value can't start or end with a doublequote
• A value can't contain special characters
  • HTTP Headers only allow ASCII characters
  • There is no option to encode/decode the values (using base64 or urlencoding)
• When a value c

Using the Web interface in Chrome (and in the Android app), and noticed this hanging out in the console:

[Deprecation] document.registerElement is deprecated and will be removed in M73, around March 2019. Please use window.customElements.define instead. See https://www.chromestatus.com/features/4642138092470272 for more details.

(anonymous) @ paper-icon-button-light.js?v=10.1.0:15

This is just nitpicky, but it would be nice to get a list of the songs that were not able to match (in the log or somewhere else).

[04:39:00] [INF] [21] Jellyfin.Plugin.Lastfm.ScheduledTasks.ImportLastfmData: Retrieved 2584 lovedTracks from LastFM for user Odinoss,
[04:38:42] [INF] [26] Jellyfin.Plugin.Lastfm.ScheduledTasks.ImportLastfmData: Syncing LastFM favourties for Odin,
[06:37:3