{"id":14,"date":"2023-12-04T06:25:48","date_gmt":"2023-12-04T09:25:48","guid":{"rendered":"https:\/\/eliasdc.dev\/?p=14"},"modified":"2023-12-15T07:15:48","modified_gmt":"2023-12-15T10:15:48","slug":"como-tratar-o-erro-xyz-para-que-o-titulo-nao-fique-muito-curto","status":"publish","type":"post","link":"https:\/\/eliasdc.dev\/index.php\/2023\/12\/04\/14\/","title":{"rendered":"How to Solve 500 – Internal Server Error in C# .NET Framework \/ .NET Core REST Requests \u2013 When Postman Works, But Your Code Falters"},"content":{"rendered":"\n

In general, a 500 – Internal Server Error isn’t a client-side problem. However, if your requests work on Postman or another API platform for developers, and you don’t have control over the server-side, you may need to adjust your app’s request to make it work as well.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Summary<\/strong><\/p>\n\n\n\n

1 – Without further ado, I will demonstrate what resolved a 500 – Internal Server Error that I was experiencing with .NET Framework.<\/p>\n\n\n\n

2 – If this doesn’t work for you, I will demonstrate how to identify possible problems for your case.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Let’s Go<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Below is what solved a problem I encountered with .NET Framework (note: this issue didn’t occur with .NET Core)<\/p>\n\n\n\n

Try setting this before making the request: <\/p>\n\n\n\n

C#<\/span><\/path><\/path><\/svg><\/span>
httpClient<\/span>.<\/span>DefaultRequestHeaders<\/span>.<\/span>ExpectContinue<\/span> = <\/span>false<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n

Code Example<\/p>\n\n\n\n
C#<\/span><\/path><\/path><\/svg><\/span>
using<\/span> (<\/span>HttpClient<\/span> <\/span>httpClient<\/span> = <\/span>new<\/span> <\/span>HttpClient<\/span>())<\/span><\/span>\n{              <\/span><\/span>\n<\/span>\n    <\/span>httpClient<\/span>.<\/span>BaseAddress<\/span> = <\/span>new<\/span> <\/span>Uri<\/span>(<\/span>"..."<\/span>);<\/span><\/span>\n<\/span>\n    <\/span>httpClient<\/span>.<\/span>DefaultRequestHeaders<\/span>.<\/span>Accept<\/span><\/span>\n        .<\/span>Add<\/span>(<\/span>new<\/span> <\/span>System<\/span>.<\/span>Net<\/span>.<\/span>Http<\/span>.<\/span>Headers<\/span>.<\/span>MediaTypeWithQualityHeaderValue<\/span>(<\/span>"application\/json"<\/span>));<\/span><\/span>\n<\/span>\n    <\/span>HttpRequestMessage<\/span> <\/span>request<\/span> = <\/span>new<\/span> <\/span>HttpRequestMessage<\/span>(<\/span>HttpMethod<\/span>.<\/span>Post<\/span>, <\/span>httpClient<\/span>.<\/span>BaseAddress<\/span>);<\/span><\/span>\n    <\/span>request<\/span>.<\/span>Content<\/span> = <\/span><\/span>\n        <\/span>new<\/span> <\/span>StringContent<\/span>(<\/span>JsonConvert<\/span>.<\/span>SerializeObject<\/span>(<\/span>objLogin<\/span>), <\/span>Encoding<\/span>.<\/span>UTF8<\/span>, <\/span>"application\/json"<\/span>);<\/span><\/span>\n\t\t<\/span><\/span>\n\t\t\/\/This ensures that the 'Expect' header isn't sent.<\/span><\/span>\n    <\/span>httpClient<\/span>.<\/span>DefaultRequestHeaders<\/span>.<\/span>ExpectContinue<\/span> = <\/span>false<\/span>;<\/span><\/span>\n\t<\/span><\/span>\n    <\/span>HttpResponseMessage<\/span> <\/span>response<\/span> = <\/span>httpClient<\/span>.<\/span>SendAsync<\/span>(<\/span>request<\/span>).<\/span>Result<\/span>;<\/span><\/span>\n<\/span>\n    <\/span>Console<\/span>.<\/span>WriteLine<\/span>(<\/span>response<\/span>.<\/span>StatusCode<\/span> + <\/span>Environment<\/span>.<\/span>NewLine<\/span> + <\/span>response<\/span>.<\/span>ToString<\/span>());<\/span><\/span>\n<\/span>\n    <\/span>Console<\/span>.<\/span>ReadKey<\/span>();<\/span><\/span>\n}<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n

Another test that worked for me was to set: <\/p>\n\n\n\n
C#<\/span><\/path><\/path><\/svg><\/span>
request<\/span>.<\/span>Version<\/span> = <\/span>HttpVersion<\/span>.<\/span>Version10<\/span>;<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
(I don’t recommend this code, but that’s not the focus of this post. Here’s an interesting discussion on the difference between HTTP versions 1.0 and 1.1: https:\/\/stackoverflow.com\/questions\/246859\/http-1-0-vs-1-1#:~:text=HTTP%201.1%20comes%20with%20persistent,this%20is%20similar%20to%20pragm<\/a>)<\/p>\n\n\n\n

Code Example<\/p>\n\n\n\n
C#<\/span><\/path><\/path><\/svg><\/span>
using<\/span> (<\/span>HttpClient<\/span> <\/span>httpClient<\/span> = <\/span>new<\/span> <\/span>HttpClient<\/span>())<\/span><\/span>\n{              <\/span><\/span>\n<\/span>\n    <\/span>httpClient<\/span>.<\/span>BaseAddress<\/span> = <\/span>new<\/span> <\/span>Uri<\/span>(<\/span>"..."<\/span>);<\/span><\/span>\n<\/span>\n    <\/span>httpClient<\/span>.<\/span>DefaultRequestHeaders<\/span>.<\/span>Accept<\/span><\/span>\n        .<\/span>Add<\/span>(<\/span>new<\/span> <\/span>System<\/span>.<\/span>Net<\/span>.<\/span>Http<\/span>.<\/span>Headers<\/span>.<\/span>MediaTypeWithQualityHeaderValue<\/span>(<\/span>"application\/json"<\/span>));<\/span><\/span>\n<\/span>\n<\/span>\n    <\/span>HttpRequestMessage<\/span> <\/span>request<\/span> = <\/span>new<\/span> <\/span>HttpRequestMessage<\/span>(<\/span>HttpMethod<\/span>.<\/span>Post<\/span>, <\/span>httpClient<\/span>.<\/span>BaseAddress<\/span>);<\/span><\/span>\n    <\/span>request<\/span>.<\/span>Content<\/span> = <\/span><\/span>\n        <\/span>new<\/span> <\/span>StringContent<\/span>(<\/span>JsonConvert<\/span>.<\/span>SerializeObject<\/span>(<\/span>objLogin<\/span>), <\/span>Encoding<\/span>.<\/span>UTF8<\/span>, <\/span>"application\/json"<\/span>);<\/span><\/span>\n    <\/span><\/span>\n    \/\/When you set the version to 1.0, headers and other request parameters change.<\/span><\/span>\n    <\/span>request<\/span>.<\/span>Version<\/span> = <\/span>HttpVersion<\/span>.<\/span>Version10<\/span>;<\/span><\/span>\n    <\/span><\/span>\n    <\/span>HttpResponseMessage<\/span> <\/span>response<\/span> = <\/span>httpClient<\/span>.<\/span>SendAsync<\/span>(<\/span>request<\/span>).<\/span>Result<\/span>;<\/span><\/span>\n<\/span>\n    <\/span>Console<\/span>.<\/span>WriteLine<\/span>(<\/span>response<\/span>.<\/span>StatusCode<\/span> + <\/span>Environment<\/span>.<\/span>NewLine<\/span> + <\/span>response<\/span>.<\/span>ToString<\/span>());<\/span><\/span>\n    <\/span><\/span>\n    <\/span>Console<\/span>.<\/span>ReadKey<\/span>();<\/span><\/span>\n}<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n

Didn’t work for you? Keep calm; now, I’ll provide you with more information on how to find a solution for your case.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n
If a request doesn’t work in your C# .NET Framework\/Core application but works in another API platform like Postman on the same machine within the same computer network, it indicates that the two requests are different. <\/p>\n\n\n\n
To discover the difference, first, try to identify all headers sent by your app and those sent by your API platform. For illustration, I will use Postman (https:\/\/www.postman.com\/<\/a>), but other platforms are similar.<\/p>\n\n\n\n

How to see the headers in Postman<\/strong>?<\/p>\n\n\n\n
In Postman, you can find it in the Headers tab or in the Console form (I prefer it in this case)<\/p>\n\n\n\n
Headers Tab:<\/em><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Console form:<\/em><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n

Now, how to see headers in you app?<\/strong><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
To make the programmer’s life easier (or not\u2026 lol), depending on the class used to make the request, some headers are added automatically. This made it difficult to discover the actual headers being sent in the request. To address this issue, I decided to create an API that receives a request and simply returns a List with the headers it received. To help you, I’ve uploaded this API on GitHub. Below are more details on how to use it:<\/p>\n\n\n\n
GitHub Repository<\/strong> Address:<\/strong> https:\/\/github.com\/eliasedc\/ApiGetHeaders<\/a> <\/p>\n\n\n\n
FYI,<\/strong> the API was developed in .NET 6, but there are also two console projects simulating clients\u2014one in .NET Framework 4.8 and another one in .NET 6.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

The solution is configured to start the three projects in the same time. I did this to demonstrate that the same request to bring different results between the .NET Framework and .NET Core clients (the Swagger works too):<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Both clients send the request in the same way (using the exact same code):<\/p>\n\n\n\n
C#<\/span><\/path><\/path><\/svg><\/span>
using<\/span> (<\/span>HttpClient<\/span> <\/span>httpClient<\/span> = <\/span>new<\/span> <\/span>HttpClient<\/span>())<\/span><\/span>\n{<\/span><\/span>\n    <\/span>httpClient<\/span>.<\/span>BaseAddress<\/span> = <\/span>new<\/span> <\/span>Uri<\/span>(<\/span>pRequestUrl<\/span>);<\/span><\/span>\n    <\/span>httpClient<\/span>.<\/span>DefaultRequestHeaders<\/span>.<\/span>Accept<\/span><\/span>\n        .<\/span>Add<\/span>(<\/span>new<\/span> <\/span>System<\/span>.<\/span>Net<\/span>.<\/span>Http<\/span>.<\/span>Headers<\/span>.<\/span>MediaTypeWithQualityHeaderValue<\/span>(<\/span>"application\/json"<\/span>));<\/span><\/span>\n<\/span>\n    <\/span>HttpRequestMessage<\/span> <\/span>request<\/span> = <\/span>new<\/span> <\/span>HttpRequestMessage<\/span>(<\/span>HttpMethod<\/span>.<\/span>Post<\/span>, <\/span>httpClient<\/span>.<\/span>BaseAddress<\/span>);<\/span><\/span>\n    <\/span>request<\/span>.<\/span>Content<\/span> =<\/span><\/span>\n        <\/span>new<\/span> <\/span>StringContent<\/span>(<\/span>JsonSerializer<\/span>.<\/span>Serialize<\/span>(<\/span>pObjToSend<\/span>), <\/span>Encoding<\/span>.<\/span>UTF8<\/span>, <\/span>"application\/json"<\/span>);<\/span><\/span>\n<\/span>\n    <\/span>HttpResponseMessage<\/span> <\/span>response<\/span> = <\/span>httpClient<\/span>.<\/span>SendAsync<\/span>(<\/span>request<\/span>).<\/span>Result<\/span>;<\/span><\/span>\n    <\/span>string<\/span> <\/span>strResult<\/span> = <\/span>response<\/span>.<\/span>Content<\/span>.<\/span>ReadAsStringAsync<\/span>().<\/span>GetAwaiter<\/span>().<\/span>GetResult<\/span>();<\/span><\/span>\n<\/span>\n    <\/span>Console<\/span>.<\/span>WriteLine<\/span>(<\/span>string<\/span>.<\/span>Join<\/span>(<\/span>Environment<\/span>.<\/span>NewLine<\/span>, <\/span>JsonSerializer<\/span>.<\/span>Deserialize<\/span><<\/span>List<\/span><<\/span>string<\/span>>>(<\/span>strResult<\/span>)));<\/span><\/span>\n<\/span>\n    <\/span>Console<\/span>.<\/span>ReadKey<\/span>();<\/span><\/span>\n}<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n

See different results:<\/strong><\/p>\n\n\n\n
.NET Core<\/em><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

.NET Framework<\/em><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Swagger<\/em><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Postman<\/em><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
If you don’t want to use the clients in your case, you can run the API and input the endpoint of your application to call this API.<\/p>\n\n\n\n

And now, what I do with this information?<\/strong><\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
<\/p>\n\n\n\n

Well, now you can compare the differences between your app’s headers and Postman’s headers. With this information, you can either insert, delete, or modify your app’s headers to match those in Postman. Alternatively, you can adjust the headers in Postman to match your app for testing purposes.<\/p>\n\n\n\n
In my case, this revealed that the ‘500 – Internal Server Error’ was caused by the ‘Expect’ header within my application.<\/p>\n\n\n\n

It don\u2019t work to me, o what more I can see?<\/strong><\/p>\n\n\n\n
You can check the TLS protocol in your API platform and force your application to use the same. 
FYI, by default, depending on your OS and which .NET version you are using, your system will try to find the best one.<\/p>\n\n\n\n
In Postman you can see it in the Console form:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n

To change the protocol used in your application, simply include the following code before sending your request<\/p>\n\n\n\n
C#<\/span><\/path><\/path><\/svg><\/span>
ServicePointManager<\/span>.<\/span>SecurityProtocol<\/span> = <\/span>SecurityProtocolType<\/span>.<\/span>Tls13<\/span>;<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n

Code Example:<\/p>\n\n\n\n
C#<\/span><\/path><\/path><\/svg><\/span>
 <\/span>ServicePointManager<\/span>.<\/span>SecurityProtocol<\/span> = <\/span>SecurityProtocolType<\/span>.<\/span>Tls13<\/span>;<\/span><\/span>\n <\/span><\/span>\n <\/span>using<\/span> (<\/span>HttpClient<\/span> <\/span>httpClient<\/span> = <\/span>new<\/span> <\/span>HttpClient<\/span>())<\/span><\/span>\n {<\/span><\/span>\n     ...<\/span><\/span>\n }<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n

That’s it<\/strong><\/p>\n\n\n\n
In this post, we will explore how to identify the causes of a 500 – Internal Server Error, possible solutions, and introduce a GitHub API to check and compare headers in your app.<\/p>\n\n\n\n
I hope that it will help you.<\/p>\n\n\n\n
See you next time!<\/p>\n\n\n\n
\"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"
In general, a 500 – Internal Server Error isn’t a client-side problem. However, if your requests work on Postman or another API platform for developers, and you don’t have control over the server-side, you may need to adjust your app’s request to make it work as well. Summary 1 – Without further ado, I will […]<\/p>\n","protected":false},"author":1,"featured_media":139,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/posts\/14"}],"collection":[{"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/comments?post=14"}],"version-history":[{"count":50,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/posts\/14\/revisions"}],"predecessor-version":[{"id":173,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/posts\/14\/revisions\/173"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/media\/139"}],"wp:attachment":[{"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/media?parent=14"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/categories?post=14"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eliasdc.dev\/index.php\/wp-json\/wp\/v2\/tags?post=14"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}