为何HttpClient.PostAsync请求失败时不抛出异常？

Great question! Let's break this down clearly and practically:

The Reason for the Behavior Difference #

This split comes down to the design intent behind each HttpClient method:

• GetStringAsync (alongside GetByteArrayAsync and GetStreamAsync) are convenience shortcut methods. Their sole purpose is to deliver successful response content with minimal boilerplate. If a non-2xx status code (like 404) comes back, the core goal of the method (fetching valid, usable content) is unachievable—so the framework automatically throws an HttpRequestException to save you from writing repetitive checks.
• PostAsync (and base methods like GetAsync, PutAsync) are flexible, low-level tools. POST requests often have nuanced use cases: you might need to parse error details from a 400 Bad Request, trigger a retry on 401 Unauthorized, or even treat a 404 as a valid business state. The framework can't assume what counts as an "exception" for your specific scenario, so it leaves the status code judgment up to you.

Elegant Handling Solutions #

You don't have to repeat that status check block every time—here are a few clean approaches:

1. Build a Reusable Async Extension Method #

Wrap the status validation logic into an extension method that you can chain onto any Task<HttpResponseMessage>:

public static async Task<HttpResponseMessage> EnsureSuccessAsync(this Task<HttpResponseMessage> responseTask)
{
    var response = await responseTask;
    if (!response.IsSuccessStatusCode)
    {
        // Include response content in the exception to simplify debugging
        var errorDetails = await response.Content.ReadAsStringAsync();
        throw new HttpRequestException(
            $"Request failed with status {(int)response.StatusCode} ({response.StatusCode}). Error content: {errorDetails}");
    }
    return response;
}

Now your code becomes concise and consistent:

var response = await _http.PostAsync("api/pollapi/request", new StringContent(requestInput))
                          .EnsureSuccessAsync();
// Proceed to process the successful response

2. Use the Built-in EnsureSuccessStatusCode (.NET 5+) #

If you're working with a newer .NET version, there's a synchronous built-in method you can leverage (though the async extension above is better for including error context):

var response = await _http.PostAsync("api/pollapi/request", new StringContent(requestInput));
response.EnsureSuccessStatusCode(); // Throws HttpRequestException for non-2xx statuses

3. Use Polly for Advanced Policies #

For complex scenarios like retries, circuit breaking, or fallback logic, the Polly library is a powerful tool. You can define a global policy to handle non-success status codes consistently across your app:

// Define a policy that retries 3 times on non-success status codes
var retryPolicy = Policy
    .HandleResult<HttpResponseMessage>(r => !r.IsSuccessStatusCode)
    .RetryAsync(3);

// Execute the request with the policy applied
var response = await retryPolicy.ExecuteAsync(
    () => _http.PostAsync("api/pollapi/request", new StringContent(requestInput)));

// Final check to throw if the request still fails after retries
response.EnsureSuccessStatusCode();

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