Flurl | Fluent URL builder and testable HTTP client for NET | HTTP Client library

It's the FreshDesk API issue. They want, for some reason, for multipart form-data parameter names to be enclosed in quotation marks. It's not a requirement per HTTP standards. RestSharp and Flurl use MultipartFormDataContent, and it adds uses parameter names as provided.

Following up on your issue, I added this property to RestRequest:

According to their docs: yes - the default usage, as you are showing, makes uses of the implementation guidelines provided by Microsoft:

Quote:

Flurl.Http is built on top of the System.Net.Http stack. If you're familiar with HttpClient, you probably already know this advice:

HttpClient is intended to be instantiated once and re-used throughout the life of an application. Especially in server applications, creating a new HttpClient instance for every request will exhaust the number of sockets available under heavy loads. This will result in SocketException errors.

Flurl.Http adheres to this guidance by default. Fluent methods like this will create an HttpClient lazily, cache it, and reuse it for every call to the same host*:

Sources:

https://flurl.dev/docs/client-lifetime/

https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclient?view=net-6.0#remarks

Keep in mind though - "heavy load" can still mean you'll hit certain limits like:

• reaching maximum server connections - i.e.: possible server overload
• reaching maximum client socket usage - i.e.: initiating too many concurrent connections

For more info see: https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.maxconnectionsperserver?view=net-6.0

This means you'll still need to do a sanity check on the amount of connections you'll be expecting.

I have fixed the issue. I forgot to set JsonProperty and make it camelCase.

Replay returns "connectable" observable, and you need to call Connect() method on it to start it going. Without that call, it does not subscribe to the underlying observable and does not emit items to its own subscribers, so that's why you have a "deadlock".

In this case instead of manually connecting, you can use RefCount() extension method which will automatically connect it on first subscriber and disconnect on when last subscriber unsubscribes. So:

You can solve this problem in the following way:

Let's suppose you have defined the different payload classes like this:

Either encoding should work, but historically + is and always has been the dominant implementation for x-www-form-urlencoded, so this is how Flurl does it. See discussion here.

I think the problem is the arrange step of your test:

multipart/form-data != JSON, so don't use PostJsonAsync. Use PostMultipartAsync. This is documented here. Here's the relevant change to what you have:

There's a few ways to add a custom message handler with Flurl (such as with a custom factory), but since you're already using IHttpClientFactory, I think the easiest path to get what you want (and the one I'd recommend) is to continue injecting HttpClient into your services as you're doing and wrap them with Flurl inside the service: