Setting URL-Encoded Form Content

Sets the request's content type to application/x-www-form-urlencoded and sends form data.

123456789101112

HttpRequestBuilder.Post("https://furion.net/")    .SetFormUrlEncodedContent(new { id = 1, name = "Furion" });HttpRequestBuilder.Post("https://furion.net/")    .SetFormUrlEncodedContent(new { id = 1, name = "Furion" }, useStringContent: true); // Uses StringContent to resolve the FormUrlEncodedContent encoding issue// Supports URL-encoded string formatHttpRequestBuilder.Post("https://furion.net/")    .SetFormUrlEncodedContent("id=1&name=furion", useStringContent: true);HttpRequestBuilder.Post("https://furion.net/")    .SetFormUrlEncodedContent(new { id = 1, name = "Furion" }, urlEncode: false); // Can be configured to skip URL encoding

Notes on URL-encoded form content

By default, URL-encoded forms are built via the FormUrlEncodedContent type, but this type does not support custom request content encoding; it uses Encoding.Latin1 instead of UTF-8 by default. This may cause exceptions when submitting to certain endpoints.

To resolve this issue, set the useStringContent parameter to true to build form data using StringContent, which allows customizing the encoding to UTF-8.
cs
```
123
```
var content = await httpRemoteService.PostAsAsync<YourRemoteModel>("https://localhost:7044/HttpRemote/AddURLForm", builder => builder .SetFormUrlEncodedContent(new { id = 1, name = "furion" }, useStringContent: true));
Some servers require an explicit character set (charset) declaration; in that case, specify the encoding via the contentEncoding parameter, for example using UTF-8:
cs
```
123
```
var content = await httpRemoteService.PostAsAsync<YourRemoteModel>("https://localhost:7044/HttpRemote/AddURLForm", builder => builder .SetFormUrlEncodedContent(new { id = 1, name = "furion" }, Encoding.UTF8));
With this setting, the following Content-Type request header is generated when sending the remote request: application/x-www-form-urlencoded; charset=UTF-8.