flurl

I start with Flurl and I would like to create a POST but I think I have a problem with the format of my JSON parameters. You can see the JSON parameters: { "aaaUser" : { "attributes" : { "name" : "device:domain\\login", "pwd" : "123456" } } } These settings work with Postman and now I would like to use Flurl to continue my little POST :) But my JSON format is not correct. using System.Threading.Tasks; using Flurl.Http; namespace Script { class Program { static async Task Main(string[] args) { var result = await "https://IP/api/aaaLogin.json".PostUrlEncodedAsync(new { name = "device:domain\

I am in need to post the following request: POST http://target-host.com/some/endpoint HTTP/1.1 Content-Type: multipart/form-data; boundary="2e3956ac-de47-4cad-90df-05199a7c1f53" Accept-Encoding: gzip, deflate Connection: Keep-Alive Content-Length: 6971 Host: target-host.com --2e3956ac-de47-4cad-90df-05199a7c1f53 Content-Disposition: form-data; name="some-label" value --2e3956ac-de47-4cad-90df-05199a7c1f53 Content-Disposition: form-data; name="file"; filename="my-filename.txt" <file contents> --2e3956ac-de47-4cad-90df-05199a7c1f53-- I can do this really easily with Python requests library as

I am using FlurlHttp and I want to disable AllowAutoRedirect for some API calls. I know How can I get System.Net.Http.HttpClient to not follow 302 redirects? WebRequestHandler webRequestHandler = new WebRequestHandler(); webRequestHandler.AllowAutoRedirect = false; HttpClient httpClient = new HttpClient(webRequestHandler); // Send a request using GetAsync or PostAsync Task<HttpResponseMessage> response = httpClient.GetAsync("http://www.google.com") But for Flurl I found only the way similar to described in C# Flurl - Add WebRequestHandler to FlurlClient (I haven't compiled yet the code below ,

Flurl states that using singleton client is recommended pattern: 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. But since Asp.Net Core 2.1 there are updated rules for HttpClient lifetime in Net Core 2.1 . When you use the HttpClientFactory to request a HttpClient, you do in fact get a new instance each time, which means we don’t have to worry about

I am using flurl to submit HTTP request and this is very useful. Now I need to change the " Content-Type" header for some of the requests to "application/json;odata=verbose" public async Task<Job> AddJob() { var flurlClient = GetBaseUrlForGetOperations("Jobs").WithHeader("Content-Type", "application/json;odata=verbose"); return await flurlClient.PostJsonAsync(new { //Some parameters here which are not the problem since tested with Postman }).ReceiveJson<Job>(); } private IFlurlClient GetBaseUrlForOperations(string resource) { var url = _azureApiUrl .AppendPathSegment("api") .AppendPathSegment