Open Feign客户端上传PDF文档损坏问题求助

Let me break down why your PDF is getting corrupted and how to fix this—this is a common pitfall when working with file uploads in Feign!

The Root Cause #

You're using Content-type: x-www-form-urlencoded for your request, but this content type is designed for text-based form data. When you send a binary file like a PDF through this encoding, it gets mangled during URL encoding (special characters are replaced, binary sequences are altered), which destroys the file's structure.

Chances are, even though you thought Postman was using the same x-www-form-urlencoded setting, it actually switched to multipart/form-data automatically when you added the file parameter—this is Postman's default behavior for file uploads, which is why it worked there.

Solution 1: Use multipart/form-data with Spring Cloud Feign (Recommended) #

If you're using Spring Cloud Feign (the most common setup), update your client interface to use multipart form data properly:

import org.springframework.cloud.openfeign.FeignClient;
import org.springframework.http.MediaType;
import org.springframework.web.bind.annotation.PostMapping;
import org.springframework.web.bind.annotation.RequestPart;
import org.springframework.web.multipart.MultipartFile;

@FeignClient(name = "your-backend-service")
public interface DocumentUploadClient {

    @PostMapping(
        value = "/url",
        consumes = MediaType.MULTIPART_FORM_DATA_VALUE
    )
    DocumentUpload uploadDocument(
        @RequestPart("string") String stringParam,
        @RequestPart("file") MultipartFile file
    );
}

Solution 2: For Native OpenFeign (No Spring Cloud) #

If you're using pure OpenFeign, you'll need to add a SpringFormEncoder to handle multipart requests:

1. First, add the necessary dependency (Maven example):

<dependency>
    <groupId>io.github.openfeign.form</groupId>
    <artifactId>feign-form</artifactId>
    <version>3.8.0</version> <!-- Use the latest compatible version -->
</dependency>

2. Configure the encoder in your Feign configuration:

import feign.codec.Encoder;
import feign.form.spring.SpringFormEncoder;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;

@Configuration
public class FeignMultipartConfig {

    @Bean
    public Encoder feignEncoder() {
        return new SpringFormEncoder();
    }
}

3. Update your client interface:

import feign.Headers;
import feign.RequestLine;
import org.springframework.web.multipart.MultipartFile;

public interface DocumentUploadClient {

    @RequestLine("POST /url")
    @Headers("Content-Type: multipart/form-data")
    DocumentUpload uploadDocument(
        @Param("string") String stringParam,
        @Param("file") MultipartFile file
    );
}

Key Notes #

• Replace MultipartFile with File only if your setup explicitly supports it—MultipartFile is the standard in Spring for handling uploaded files.
• Enable Feign's full logging to verify request headers and payload match Postman's. Set logging.level.your.client.package=DEBUG in application.properties to see the actual request details.

By switching to multipart/form-data, you're sending the file as raw binary data wrapped in proper multipart boundaries, which preserves the PDF's integrity—just like Postman was doing under the hood.

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