Todd Menier

I did some experimenting per the above ideas and didn't like where things were going. It occurred to me that something along the lines of [named clients](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/http-requests#named-clients) is really all...

Closing in favor of #770. Flurl is getting a BIG overhaul in this area and I encourage you weigh in there with any thoughts you may have.

Dusting this one off and giving it some love (finally!) for 4.0. There's another issue (#639) that could really benefit from having a simpler way to access the `HttpRequestMessage` just...

I will reconsider. #639 was easy to solve in a more direct way using the Settings objects, and I'll consider a more direct solution for this one as well. In...

Good news: direct support for HTTP version will make the 4.0 cut. I think it's a good fit for Flurl's [configuration pattern](https://flurl.dev/docs/configuration/) so it can be available at the request,...

@SeanKilleen Thanks again for the helpful start on this. I added my own bits to the process and I think I hit a balance of automated and manual steps that...

Now available in prerelease 4 https://www.nuget.org/packages/Flurl/4.0.0-pre4

@michalberezowski There are plans in the works for an ASP.NET Core companion lib that would bring FlurlClient configuration all the way up to the service registration layer and follow many...

Oops, you're right...the example I gave shows how you would get it to work with [typed clients](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/http-requests#typed-clients); it's slightly different with [named clients](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/http-requests#named-clients) but same basic idea - follow the...

I'm cutting some of the bigger non-breaking enhancements originally planned for 4.0 in the interest of getting it released sooner. I still think this is a good idea and it'll...