SpringBoot代理Multipart请求时下游服务参数解析失败问题

我在SpringBoot的代理控制器中编写了如下方法，尝试将请求代理至下游服务：

@PostMapping(value = "/**",
        consumes = {MediaType.APPLICATION_JSON_VALUE, MediaType.MULTIPART_FORM_DATA_VALUE},
        produces = MediaType.APPLICATION_JSON_VALUE)
ResponseEntity proxyPostRequest(@RequestHeader HttpHeaders requestHeaders, HttpServletRequest request, ProxyExchange<String> proxy) throws Exception {
    requestHeaders.addIfAbsent("x-program-id", request.getAttribute("programId").toString());
    // required for host header match
    requestHeaders.remove(HttpHeaders.HOST);
    requestHeaders.add(HttpHeaders.HOST, host);
    proxy.headers(requestHeaders);
    final URI uri = new URI(scheme, null, host, Integer.valueOf(port), request.getRequestURI(), request.getQueryString(), null);
    ResponseEntity responseEntity = proxy.uri(uri).post();
    return enrichResponse(responseEntity);
}

但下游服务抛出错误：

Could not resolve parameter [0] in public org.springframework.http.ResponseEntity 

直接调用下游服务的相同API却能正常运行，说明反向代理的请求处理存在问题。测试用的curl请求如下：

curl --location 'http://localhost:8080/test/path/'\
--form 'logoFile=@"path-to-file.txt"' \
--form 'message="hello"'

问题原因 #

这个错误源于Multipart请求的参数解析逻辑与普通JSON请求存在差异，当前代理代码未正确处理Multipart请求的参数传递流程，导致下游服务无法解析请求中的参数：

1. 处理multipart/form-data请求时，Spring需要将请求体中的表单数据解析为参数，但现有代码仅转发了请求头，未正确传递Multipart请求体内容，且ProxyExchange<String>默认不支持Multipart类型的请求处理。
2. @RequestHeader HttpHeaders requestHeaders虽能获取请求头，但Multipart请求的请求体处理需要额外的配置支持，现有实现未覆盖该场景。

解决方法 #

方法1：调整ProxyExchange泛型并适配Multipart请求 #

将ProxyExchange<String>改为ProxyExchange<MultipartHttpServletRequest>，利用Spring对Multipart请求的原生支持传递表单数据，修改后的代码如下：

@PostMapping(value = "/**",
        consumes = {MediaType.APPLICATION_JSON_VALUE, MediaType.MULTIPART_FORM_DATA_VALUE},
        produces = MediaType.APPLICATION_JSON_VALUE)
ResponseEntity proxyPostRequest(@RequestHeader HttpHeaders requestHeaders, 
                                MultipartHttpServletRequest request, 
                                ProxyExchange<MultipartHttpServletRequest> proxy) throws Exception {
    requestHeaders.addIfAbsent("x-program-id", request.getAttribute("programId").toString());
    requestHeaders.remove(HttpHeaders.HOST);
    requestHeaders.add(HttpHeaders.HOST, host);
    proxy.headers(requestHeaders);
    
    // 构建下游服务目标URI
    final URI uri = new URI(scheme, null, host, Integer.valueOf(port), 
                           request.getRequestURI(), request.getQueryString(), null);
    
    // 转发Multipart请求的文件和表单参数
    ResponseEntity responseEntity = proxy.uri(uri).post(request::getMultipartFiles);
    return enrichResponse(responseEntity);
}

方法2：使用RestTemplate手动转发Multipart请求 #

若ProxyExchange方式适配困难，可直接用RestTemplate实现请求转发，对Multipart和JSON请求分别处理，灵活性更高：

@Autowired
private RestTemplate restTemplate;

@PostMapping(value = "/**",
        consumes = {MediaType.APPLICATION_JSON_VALUE, MediaType.MULTIPART_FORM_DATA_VALUE},
        produces = MediaType.APPLICATION_JSON_VALUE)
ResponseEntity proxyPostRequest(@RequestHeader HttpHeaders requestHeaders, 
                                HttpServletRequest request) throws Exception {
    // 统一处理请求头
    requestHeaders.addIfAbsent("x-program-id", request.getAttribute("programId").toString());
    requestHeaders.remove(HttpHeaders.HOST);
    requestHeaders.add(HttpHeaders.HOST, host);
    
    // 拼接下游服务目标URL
    StringBuilder targetUrl = new StringBuilder(scheme)
            .append("://").append(host).append(":").append(port)
            .append(request.getRequestURI());
    if (request.getQueryString() != null) {
        targetUrl.append("?").append(request.getQueryString());
    }
    
    ResponseEntity responseEntity;
    if (request instanceof MultipartHttpServletRequest multipartRequest) {
        // 处理Multipart请求：封装文件和表单参数
        MultiValueMap<String, Object> requestBody = new LinkedMultiValueMap<>();
        // 添加上传文件
        multipartRequest.getMultipartFiles().forEach(requestBody::addAll);
        // 添加普通表单参数
        multipartRequest.getParameterMap().forEach((key, values) -> {
            for (String value : values) {
                requestBody.add(key, value);
            }
        });
        responseEntity = restTemplate.postForEntity(targetUrl.toString(), new HttpEntity<>(requestBody, requestHeaders), Object.class);
    } else {
        // 处理JSON请求：读取请求体并转发
        String requestBody = StreamUtils.copyToString(request.getInputStream(), StandardCharsets.UTF_8);
        responseEntity = restTemplate.postForEntity(targetUrl.toString(), new HttpEntity<>(requestBody, requestHeaders), Object.class);
    }
    
    return enrichResponse(responseEntity);
}

额外注意事项 #

• 确保下游服务的Multipart配置（如文件大小限制、临时存储路径等）与代理服务保持一致。
• 若使用ProxyExchange方式，需确保项目引入了对应代理组件的依赖（如spring-cloud-starter-gateway或spring-cloud-starter-netflix-zuul）。
• 调试时可打印请求头和请求体内容，确认参数是否正确传递至下游服务。

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