Apollo Federation子图文件上传报错：Missing multipart field 'operations' 求助

Hey there, let's work through this file upload problem you're hitting with Apollo Federation! I've run into similar quirks before, so let's break down possible fixes step by step.

First, let's recap your scenario:

• Direct requests to your subgraph work fine for file uploads
• Using RemoteGraphQLDataSource throws BadRequestError: Missing multipart field ‘operations’
• Switching to FileUploadDataSource from @profusion/apollo-federation-upload still triggers the same error

Here are the most likely culprits and fixes:

1. Ensure Your Gateway's Apollo Server Supports Multipart Requests #

The gateway itself needs to properly parse multipart/form-data requests before forwarding them to subgraphs. If you're using Apollo Server v3+, it includes built-in upload support, but double-check your server configuration isn't disabling it:

import { ApolloGateway } from '@apollo/gateway';
import { ApolloServer } from 'apollo-server';
import FileUploadDataSource from '@profusion/apollo-federation-upload';

const gateway = new ApolloGateway({
  serviceList: [{ name: 'your-subgraph', url: 'http://localhost:4010' }],
  buildService: ({ url }) => new FileUploadDataSource({ 
    url, 
    useChunkedTransfer: true 
  }),
});

// Critical: Make sure your Apollo Server instance doesn't block uploads
const server = new ApolloServer({
  gateway,
  // For v3+, no extra upload config is needed unless you explicitly disable it
  // Avoid adding express.json()/urlencoded() middleware here—they'll break multipart parsing
});

server.listen().then(({ url }) => {
  console.log(`Gateway running at ${url}`);
});

If you're on an older Apollo Server version (v2), add uploads: true to your ApolloServer config to enable multipart handling.

2. Verify Subgraph Type Definitions & Upload Setup #

Even though direct requests work, confirm your subgraph has the required scalar and mutation definitions:

# In your subgraph's schema
scalar Upload

type Mutation {
  uploadFile(file: Upload!): FileMetadata!
}

Also, ensure your subgraph's Apollo Server isn't restricting uploads (for v3+, this is enabled by default; for v2, use uploads: true).

3. Check for Middleware Conflicts #

If your gateway uses an Express server under the hood, make sure you aren't adding middleware that parses multipart requests before Apollo Server gets to them. Middleware like express.json() or express.urlencoded() will consume the multipart request body, leaving nothing for the gateway to forward to the subgraph.

Remove any such middleware from your gateway's Express app if present.

4. Validate Version Compatibility #

Mismatched versions between @apollo/gateway and @profusion/apollo-federation-upload can cause unexpected issues. Run npm list @apollo/gateway @profusion/apollo-federation-upload to check versions, and ensure they're compatible (check the package's README for supported gateway versions).

If you find a mismatch, update the packages to compatible versions and reinstall dependencies.

5. Debug Request Forwarding #

To confirm the gateway is forwarding the multipart request correctly:

1. Use a tool like Postman or curl to send an upload request directly to the subgraph, and capture the request headers/body.
2. Send the same request to the gateway, and use a proxy tool (like Charles Proxy) or logging in your subgraph to inspect the incoming request from the gateway.

Look for missing operations or map fields in the multipart form data—this will confirm if the gateway is mangling the request during forwarding.

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