遇java.net.HttpRetryException异常，新用户创建测试接口调用失败求因

Hey there, let's dig into this error you're facing. That specific exception tells us your client is trying to retry an authenticated request, but can't because the request is being sent in streaming mode—here are the most probable causes, even if you don't recall recent changes:

Key Causes to Investigate #

1. Streaming Mode & Authentication Retry Conflict #

When your test case sends a request in streaming mode (think large request bodies, multipart/form-data, or requests where the payload is sent as an unbuffered stream), the HTTP client can't retry the request if the server returns an authentication challenge (like a 401 Unauthorized). This is because the request body stream can't be reset or re-sent once it's been consumed.

Even if you didn't intentionally change this, indirect changes might have triggered it:

• The user creation API now accepts larger payloads (like profile images) that force streaming
• A message converter in your app was updated to use streaming by default

2. Unintentional WebSecurity Changes #

It's possible someone on your team adjusted the WebSecurity config, or a dependency update altered default behavior:

• New authentication filters: If a pre-authentication filter was added, it might be returning a 401 before the request reaches your controller, triggering a retry that fails in streaming mode
• Modified authorization rules: Maybe the user creation endpoint now requires authentication, but your test case isn't sending valid credentials—leading to a 401 and failed retry
• CSRF configuration tweaks: Changes to CSRF protection could be intercepting requests and triggering retry logic that clashes with streaming

3. HttpClient Retry Policy Changes #

If your test uses Spring's RestTemplate, WebClient, or raw HttpClient, recent updates might have modified retry behavior:

• A dependency upgrade (like Spring Boot or Apache HttpClient) could have changed the default retry strategy to attempt retries for authentication errors
• A custom retry interceptor was added to test code without accounting for streaming requests

4. Request Payload Handling Shifts #

If your API now processes the request body as a stream (e.g., using @RequestBody with a streaming message converter), the client can't re-send the payload for a retry—even if it wanted to.

Steps to Diagnose & Fix #

1. Check the test request: Is your test sending a large or multipart payload? If so, that's likely triggering streaming mode. Try simplifying the payload temporarily to see if the error goes away.
2. Audit your WebSecurity config: Verify if:
   • The user creation endpoint's authorization rules changed (e.g., from permitAll() to authenticated)
   • Any new authentication filters were added
   • CSRF settings were modified (like enabling it for endpoints that didn't require it before)
3. Adjust client retry behavior: If the issue is retry + streaming conflict, configure your HTTP client to skip retries for non-repeatable requests. For example, with Apache HttpClient and RestTemplate:

   // Custom retry handler that skips streaming requests
   public class NoStreamingRetryHandler extends DefaultRetryHandler {
       @Override
       public boolean isRequestSentRetryable(HttpRequest request) {
           // Only retry if the request body can be re-sent
           if (request instanceof HttpEntityEnclosingRequest) {
               HttpEntityEnclosingRequest enclosingRequest = (HttpEntityEnclosingRequest) request;
               return enclosingRequest.getEntity().isRepeatable();
           }
           return super.isRequestSentRetryable(request);
       }
   }
   
   // Apply the handler to your RestTemplate
   HttpClient httpClient = HttpClientBuilder.create()
           .setRetryHandler(new NoStreamingRetryHandler())
           .build();
   RestTemplate restTemplate = new RestTemplate(new HttpComponentsClientHttpRequestFactory(httpClient));
   

4. Ensure valid authentication in tests: If the endpoint now requires auth, update your test case to send valid credentials (like JWT tokens or basic auth headers) to avoid the 401 that triggers the retry.

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