GET请求在HttpWebRequest与Postman正常，在HttpClient/RestSharp异常

Let’s figure out why your HttpClient and RestSharp calls aren’t working, especially since HttpWebRequest and Postman are successful. The problem almost always boils down to subtle differences in how each library handles request headers and default behaviors. Here’s how to fix and debug it:

1. Understand the Key Differences from Your Working Code #

Your HttpWebRequest explicitly clears all headers first with httpWebRequest.Headers.Clear();, then adds only the headers you need. HttpClient and RestSharp both add default headers automatically (like User-Agent, Accept-Encoding) that might be triggering a rejection from the API—some services are strict about unexpected headers.

2. Fix Your HttpClient Implementation #

Make sure you’re mirroring the exact header setup from your working code, including clearing default headers if needed. Here’s the corrected code:

using System.Net.Http;
using System.Net.Http.Headers;

// Create a new HttpClient instance (avoid reusing a client with pre-existing headers if possible)
var httpClient = new HttpClient();

// Clear default headers to match HttpWebRequest's clean slate
httpClient.DefaultRequestHeaders.Clear();

// Add the required headers
httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
httpClient.DefaultRequestHeaders.Add("api-key", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXX");

// Send the request
try
{
    var response = await httpClient.GetAsync("https://api-sandbox.grnconnect.com/api/v3/countries");
    response.EnsureSuccessStatusCode(); // Throws an exception for 4xx/5xx status codes
    var responseContent = await response.Content.ReadAsStringAsync();
    // Process your response here
}
catch (HttpRequestException ex)
{
    // Debug the error: check ex.Message or response.StatusCode
    Console.WriteLine($"Request failed: {ex.Message}");
}

Important Notes:

• If you’re using a static HttpClient (best practice for performance), ensure its default headers aren’t polluted with other values from previous requests.
• GET requests don’t technically need a Content-Type header—your HttpWebRequest sets it, but the API might be ignoring it. Skip adding it in HttpClient unless you confirm it’s required.

3. Fix Your RestSharp Implementation #

RestSharp has its own default header logic, so you’ll need to explicitly clear and set headers to match your working request. Here’s the right approach:

using RestSharp;

var restClient = new RestClient("https://api-sandbox.grnconnect.com");
var request = new RestRequest("/api/v3/countries", Method.Get);

// Clear any default headers RestSharp adds automatically
request.ClearHeaders();

// Add only the headers your API needs
request.AddHeader("Accept", "application/json");
request.AddHeader("api-key", "XXXXXXXXXXXXXXXXXXXXXXXXXXXXX");

// Send the request
try
{
    var response = await restClient.ExecuteAsync(request);
    if (!response.IsSuccessful)
    {
        // Debug with status code and error details
        Console.WriteLine($"Error: {response.StatusCode} - {response.ErrorMessage}");
        Console.WriteLine($"Response body: {response.Content}");
    }
    else
    {
        var responseContent = response.Content;
        // Process your response here
    }
}
catch (Exception ex)
{
    Console.WriteLine($"Request failed: {ex.Message}");
}

Critical Tip:
Don’t add a Content-Type header to your GET request in RestSharp. Unlike HttpWebRequest, RestSharp might handle this header differently for GET calls, and many APIs reject Content-Type on GET requests entirely.

4. Debugging Steps to Pinpoint the Exact Issue #

If the above code still fails, use these steps to find the root cause:

• Capture and compare requests: Use a tool like Fiddler or Wireshark to record the request sent by HttpClient/RestSharp, then compare it side-by-side with the working Postman/HttpWebRequest request. Look for missing headers, extra headers, or header casing differences (some APIs incorrectly enforce case sensitivity).
• Inspect the error response: Always check the status code (e.g., 401 = invalid api-key, 400 = bad request) and response body. The API might return a detailed error message that tells you exactly what’s wrong.
• Test with minimal headers: Strip down the request to only the mandatory headers (api-key and Accept) and see if it works. Add headers one by one to identify which one is causing the problem.

内容的提问来源于stack exchange，提问作者Toji Thomas