[BUG] AddRefitClient doesn't use the AuthorizationHeaderValueGetter

[Elfocrash]

Describe the bug
If I use the AddRefitClient to register my client then the AuthorizationHeaderValueGetter isn't used.

I have the following interface and the following settings:

[Headers("Authorization: Bearer")]
public interface ISomeApi
{
    [Get("/users/{user}")]
    Task<ApiResponse<User>> GetUser(string user);
}

var refitSettings = new RefitSettings
{
    AuthorizationHeaderValueGetter = () => Task.FromResult("AuthKey")
};

If i call RestService.For<ISomeApi>("https://api.test.com", refitSettings) then my call is properly populated with the Authorization header having a value Bearer AuthKey.

However if I use the same ISomeApi interface using the AddRefitClient like this services.AddRefitClient<ISomeApi>(refitSettings); then the Authorization header's value is Bearer. The getter is never invoked to set the value.

Expected behavior
Both RestService.For and AddRefitClient should be utilizing the settings in the same way and the header should be populated.

Environment

• OS: Windows 10 Pro
• Version 10.0.17134
• Device: PC

[Styxxy]

Might be similar like #574 , because of the HttpClientFactory. To be determined though.

[Elfocrash]

After some debugging it looks like the AddRefitClient path completely ignores the Handler selection

[endeffects]

@onovotny @Elfocrash Any progress here?

[Elfocrash]

I had to do some DI hack locally to get this to work on my project but no actual fix yet. Both AuthorizationHeaderValueGetter and the other requestMessage one are not working.

[endeffects]

@onovotny Could you please have a look into this? Refit should be able to override this HttpClientFactory settings especially for authorization.

[clairernovotny]

PR's with related unit tests are welcome!

I've been busy and haven't had time to look into this.

[clairernovotny]

Fixed by #861