-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for using a custom HttpClient or HttpMessageHandler #1
Comments
Adding a custom HttpClient is possible. Do you also need another option to provide a custom HttpMessageHandler? |
Having both options would be nice, but I'd prefer the ability to use a custom |
I did update the constructors, please take a look if this is fine for you. (See latest code in this github project) |
Seems to be what I was looking for 👍 . Just one thing, can you please add an additional net46 target which uses the |
You want the 4.3.0 versipn I guess? And only for 4.6 ? |
I think that a lower version might be fine. You can always upgrade yourself, but a downgrade gets difficult. |
For now I just used 4.3.0 See NuGet from this feed: If this one works fine; I will upload to real NuGet |
Works fine with my ASP.NET Core test project |
Can you also chexk for a 462 project? |
Sure, but not today anymore. |
Running tests in a net462 project works too. |
Uploaded to NuGet.org |
It would be useful when you would be able to provide a custom HttpClient or HttpMessageHandler. This would allow the usage of the client in the following scenarios:
The text was updated successfully, but these errors were encountered: