Request Modifier not reached when chained with ConfigurePrimaryHttpMessageHandler

[stephenstroud]

Any ideas? I need the ConfigurePrimaryHttpMessageHandler for self signed cert purposes.

            services.AddRestEaseClient<T>(baseAddress,
                client => { },

                 async (request, cancellationToken) => {                     
                    //do some request changes
                 })
                .ConfigurePrimaryHttpMessageHandler(() => new HttpClientHandler
                 {
                     ClientCertificateOptions = ClientCertificateOption.Manual,
                     ServerCertificateCustomValidationCallback =
                    (httpRequestMessage, cert, cetChain, policyErrors) => {
                        return true;
                    }
                 });

[stephenstroud]

This is kind of related to Issue

Looks like the .ConfigurePrimaryHttpMessageHandler is configured after, but then how do I configure the cert?

[stephenstroud]

In the end I took inspiration in this class and made it work by introducing the ServerCertificateCustomValidationCallback within the constructor.

[canton7]

Yep it's the same issue. I'll get that fixed in the next release.

[canton7]

(this issue will get closed automatically when the release goes out)