HTTP Authorization in web sources

More and more APIs and web pages require a token, and more and more of those don't support a token via the calling URI, but rather via the HTTP Authorization header.

I see that the Discogs web source uses what I guess is a sort of proxy on mp3tag.de server to inject it.

My suggestion is to add something like [Authorization]= keyword to the web source framework which could create the "Authorization: " header. This will at least solve the situation where a static token is an option.

1 Like

I'm using OAuth for Discogs and it's handled from within Mp3tag. The proxy you're referring to is an image proxy that keeps load from the Discogs servers and prevents users from being blocked due to rate-limiting.

Do you have a particular use case for the HTTP Authorization?

To access Apple Music API the access must be authorized through HTTP headers.