alibaba/nacos · error · IllegalArgumentException

Unsupported HTTP method: {}

Error message

Unsupported HTTP method: {}

What it means

Thrown by ClientHttpProxy.executeHttpRequest as an IllegalArgumentException in the default branch of the HTTP method switch. It fires when the HttpRequest's HTTP method is not one of GET, POST (json/form/multipart), PUT, or DELETE. This is a programming error indicating an unsupported or misspelled HTTP method was set on the request.

Source

Thrown at maintainer-client/src/main/java/com/alibaba/nacos/maintainer/client/remote/ClientHttpProxy.java:242

        
        switch (request.getHttpMethod()) {
            case HttpMethod.GET:
                return nacosRestTemplate.get(url, httpConfig, httpHeaders, query, String.class);
            case HttpMethod.POST:
                if (StringUtils.isNotBlank(request.getBody())) {
                    return nacosRestTemplate.postJson(url, httpHeaders, query, request.getBody(),
                        String.class);
                } else {
                    return nacosRestTemplate.postForm(url, httpConfig, httpHeaders, paramValues,
                        String.class);
                }
            case HttpMethod.PUT:
                return nacosRestTemplate.putForm(url, httpConfig, httpHeaders, paramValues,
                    String.class);
            case HttpMethod.DELETE:
                return nacosRestTemplate.delete(url, httpConfig, httpHeaders, query, String.class);
            default:
                throw new IllegalArgumentException(
                    "Unsupported HTTP method: " + request.getHttpMethod());
        }
    }
    
    private static final String LINE_FEED = "\r\n";
    
    private static final String BOUNDARY_PREFIX = "----NacosBoundary";
    
    private HttpRestResult<String> executeMultipartPost(String url, HttpClientConfig httpConfig,
        Header httpHeaders,
        Query query, HttpRequest request) throws IOException {
        String fullUrl = query != null && !query.isEmpty() ? url + "?" + query.toQueryUrl() : url;
        String boundary = BOUNDARY_PREFIX + System.currentTimeMillis();
        
        java.net.URL urlObj = new java.net.URL(fullUrl);
        HttpURLConnection conn = (HttpURLConnection) urlObj.openConnection();
        conn.setRequestMethod(HttpMethod.POST);
        conn.setConnectTimeout(httpConfig.getConTimeOutMillis());

View on GitHub (pinned to 9b989acdf1)

Solutions

1. Ensure the HttpRequest uses only GET, POST, PUT, or DELETE methods.
2. If PATCH or another method is genuinely needed, extend ClientHttpProxy or file a feature request — the current proxy does not support it.
3. Audit the code that constructs the HttpRequest to confirm the HTTP method is always from the supported HttpMethod constants.

Set<String> supported = Set.of(HttpMethod.GET, HttpMethod.POST, HttpMethod.PUT, HttpMethod.DELETE);
if (!supported.contains(request.getHttpMethod())) {
    throw new IllegalArgumentException("Unsupported HTTP method: " + request.getHttpMethod());
}

boolean isSupportedHttpMethod(String method) {
    return method != null && Set.of(HttpMethod.GET, HttpMethod.POST, HttpMethod.PUT, HttpMethod.DELETE)
        .contains(method);
}

When it happens

Trigger: Building an HttpRequest with request.setHttpMethod() set to a value outside the supported set (GET, POST, PUT, DELETE) — e.g. PATCH, HEAD, OPTIONS, or a custom method string. The switch in executeHttpRequest has no case for it and falls to default.

Common situations: Custom plugin or extension code building an HttpRequest with PATCH or HEAD method. A bug where the HTTP method constant is set from an untrusted source. Version mismatch where a new method was expected but the proxy does not support it.

Related errors

• 20002
• 10000
• 20002
• 10000
• 20002

AI-assisted analysis of alibaba/nacos@9b989acdf1 (2026-08-14). Data as JSON: /api/errors/5b53c119edcca3dc. Report an issue: GitHub.