Spring Boot控制器调用第三方GraphQL API遇400错误求助

Hey there! Let's figure out why you're hitting that 400 Bad Request error when calling the third-party GraphQL API from your Spring Boot controller. From the partial code you shared, there are a few common issues that usually cause this—let's break them down and fix them step by step.

Common Causes of 400 Error for GraphQL Requests #

First, let's cover the most frequent reasons GraphQL APIs return 400:

• Missing or incorrect Content-Type header (GraphQL requires application/json)
• Malformed request body (missing required query field, invalid JSON syntax, or wrong structure)
• Invalid GraphQL query syntax (even a tiny typo in your query will trigger a 400)
• Missing required variables if your query uses them

Fixed Code Example #

Here's a revised version of your code that addresses these common issues, plus proper resource management to avoid leaks:

@SuppressWarnings("unchecked")
@RequestMapping(value = "/graphQLTest", method = RequestMethod.POST) // Explicitly set POST since GraphQL uses POST
public ResponseEntity<?> testGraphQL() throws JsonProcessingException {
    // 1. Define your valid GraphQL query (replace with your actual query)
    String graphqlQuery = "query { yourTargetQuery { id name } }";
    
    // 2. Build the standard GraphQL request body
    Map<String, Object> requestBody = new HashMap<>();
    requestBody.put("query", graphqlQuery);
    // Add variables if your query needs them:
    // requestBody.put("variables", Map.of("userId", 123));

    // Serialize the request body to JSON
    ObjectMapper objectMapper = new ObjectMapper();
    String requestJson = objectMapper.writeValueAsString(requestBody);

    // Use try-with-resources to auto-close HTTP client/response (avoids resource leaks)
    try (CloseableHttpClient client = HttpClients.createDefault()) {
        HttpPost httpPost = new HttpPost("http://172.30.66.149:3000/graphql");
        
        // 3. Set critical request headers
        httpPost.setHeader(HttpHeaders.CONTENT_TYPE, MediaType.APPLICATION_JSON_VALUE);
        // Add Authorization header if the API requires authentication:
        // httpPost.setHeader(HttpHeaders.AUTHORIZATION, "Bearer your-auth-token");

        // 4. Attach the JSON request body
        StringEntity requestEntity = new StringEntity(requestJson, ContentType.APPLICATION_JSON);
        httpPost.setEntity(requestEntity);

        // 5. Execute the request and handle the response
        try (CloseableHttpResponse response = client.execute(httpPost)) {
            HttpEntity responseEntity = response.getEntity();
            if (responseEntity != null) {
                String responseJson = EntityUtils.toString(responseEntity);
                // Parse and return the response as needed
                return ResponseEntity.ok(responseJson);
            } else {
                return ResponseEntity.noContent().build();
            }
        } finally {
            // Ensure response resources are released
            EntityUtils.consume(response.getEntity());
        }
    } catch (IOException e) {
        e.printStackTrace();
        return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR)
                .body("Failed to call GraphQL API: " + e.getMessage());
    }
}

Key Fixes Explained #

• Explicit POST Method: GraphQL APIs almost always expect POST requests, so we added method = RequestMethod.POST to the @RequestMapping annotation.
• Valid Request Headers: We set the mandatory Content-Type: application/json header—this is one of the most common reasons for 400 errors if missing.
• Proper Request Body Structure: We built a standard GraphQL request object with the required query field (and optional variables if needed).
• Resource Management: Used try-with-resources for CloseableHttpClient and CloseableHttpResponse to automatically clean up resources, preventing leaks.

Additional Troubleshooting Steps #

If you still get a 400 after applying these fixes:

1. Test Your Query in Isolation: Use Postman or the GraphQL Playground (if the API provides it) to run your query directly. If it fails here, your query has syntax issues—fix that first.
2. Compare Request Details: Use tools like Spring Boot's logging to capture the exact request your controller sends, then compare it to the working Postman request. Look for differences in headers, JSON structure, or query syntax.
3. Check for Required Variables: If your query uses variables (like query GetUser($id: ID!) { user(id: $id) { ... } }), make sure you're including the variables field in your request body with the correct values.

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