Allow HttpClient Headers configuration per request

Description

In some cases, https://github.com/luberda-molinet/FFImageLoading/wiki/Authentication-Support does not suffice the needs for authentication. For example, you need to load images with authentication parameters that are different from time to time. This gets quite tricky when using a custom HttpClientHandler.

I’d suggest adding the option to configure the default Headers in the CachedImage.

Example:

var img = new CachedImage {
    Source = new UriImageSource {
        Uri = "https://secure.example.com/image.jpg"
    },
    Headers = {
        Authorization = new AuthenticationHeaderValue("Basic", "dXNlcjpwYXNz")
    }
};

Basic Information

• Version with issue: Up to current (v2.4.3.840)
• Last known good version: N/A
• Platform: All

[ilight]

I just started using FFImageLoading for my Xamarin.iOS app and I’m stuck right here. Only few requests need to have Authorization headers but not all. Looking for a workaround at least.

[DavidStrickland0]

So for those “Looking for a work around” as the Op points out a Custom HttpClientHandler will work its just painful. But its such a common issue because of the way MS created the HttpClient it crops up in almost every project. With an HttpClientHandler you can intercept the request just before it goes out on the wire, alter it however you want and then put it back onto the wire. In the SendAsync Method of the HttpClientHandler check the Request Body or Uri and add whatever header you need. You pass in anything you need (IE Credential sets) on the constructor of the Handler and then apply them based on whatever analysis you do inside the sendasync method. It works… its just painful and none intuitive.