如何在 SI HttpRequestExecutingMessageHandler 中处理 "Transfer-Encoding=chunked"

how to handle "Transfer-Encoding=chunked" in SI HttpRequestExecutingMessageHandler

我正在使用 HttpRequestExecutingMessageHandler 调用外部服务器。我正在使用 JSON 到 object 转换器来转换 JSON 数据。但我收到以下异常。

Caused by: com.fasterxml.jackson.core.JsonParseException: Illegal character ((CTRL-CHAR, code 31)): only regular white space (\r, \n, \t) is allowed between tokens at [Source: (String)"�

当我查看 header 时,我发现了以下内容。 Transfer-Encoding=分块

这是异常日志的原因吗?

出站网关和JsonToObjectTransformer如下:

    @ServiceActivator(inputChannel = "channelOutboundRequest")
    @Bean
    public HttpRequestExecutingMessageHandler outboundGateway() {
        final HttpRequestExecutingMessageHandler handler = new HttpRequestExecutingMessageHandler(
                endpoint);
        handler.setExpectedResponseType(String.class);
        handler.setHttpMethod(HttpMethod.POST);
        handler.setOutputChannelName("channelResponse");
        handler.setAdviceChain(Collections.singletonList(advice()));
        return handler;
    }
    @Bean
    @Transformer(inputChannel = "channelResponse", outputChannel = "channelReply")
    public JsonToObjectTransformer transformer(ObjectMapper objectMapper) {
        final JsonObjectMapper<?, ?> mapper = new Jackson2JsonObjectMapper(objectMapper);
        return new JsonToObjectTransformer(DetailsDTO.class, mapper);
    }

如果问题是由 header 引起的,我该如何处理响应?

注意:如果我直接使用 postman 访问外部服务器,我会收到 JSON 结构中的响应。

我不知道这里出了什么问题。如果我使用如下所示的简单重新模板调用,它会正常工作。

JSONObject jsonObject = new JSONObject("{\"code\":\"F001\",\"transactionId\":\"1008566223232\"}");
        HttpHeaders headers = new HttpHeaders();
        headers.setContentType(MediaType.APPLICATION_JSON);
        headers.setBearerAuth("token");
        HttpEntity<String> request = 
                  new HttpEntity<String>(jsonObject.toString(), headers);
        String respns = restTemplt.postForObject("http://endpoint", request, String.class);
        System.out.println(respns);
        JSONObject response = new JSONObject(respns);

我发现的一个区别是响应 header。如下所示:

Outbound gateway response headers :- {Transfer-Encoding=chunked, http_requestMethod=GET, errorChannel=org.springframework.messaging.core.GenericMessagingTemplate$TemporaryReplyChannel@d8b195e, Server=nginx, Accept=/, Connection=keep-alive, User-Agent=PostmanRuntime/7.28.0, Host=localhost:8901, Accept-Encoding=gzip, deflate, br, http_statusCode=200 OK, Date=1622533072000, Authorization=Bearer token, replyChannel=org.springframework.messaging.core.GenericMessagingTemplate$TemporaryReplyChannel@d8b195e, Cache-Control=no-cache, ETag=W/"1009-5SzdL+uWyY6ZcMWht5dMtm2Sxlc", Content-Encoding=gzip, http_requestUrl=http://inboundurl, id=be07fc8d-d478-5fa9-33e4-61a2b5f92468, Content-Length=207, contentType=application/json;charset=utf-8, Content-Type=application/json, requestFrom=CUSTOM_HEADER, timestamp=1622533092827}

Normal restTemplate call response header [Server:"nginx", Date:"Tue, 01 Jun 2021 07:34:54 GMT", Content-Type:"application/json; charset=utf-8", Content-Length:"4105", Connection:"keep-alive", Access-Control-Allow-Origin:"*", Content-Security-Policy:"default-src 'self';base-uri 'self';block-all-mixed-content;font-src 'self' https: data:;frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests", X-DNS-Prefetch-Control:"off", Expect-CT:"max-age=0", X-Frame-Options:"SAMEORIGIN", Strict-Transport-Security:"max-age=15552000; includeSubDomains", X-Download-Options:"noopen", X-Content-Type-Options:"nosniff", X-Permitted-Cross-Domain-Policies:"none", Referrer-Policy:"no-referrer", X-XSS-Protection:"0", ETag:"W/"1009-llD9DqxYkEsjyikWajYk+16cb1k""]

有人可以帮忙吗?

经过多次尝试和错误,我找到了原因。 Accept-Encoding=gzip,deflate,br出站网关请求中的这个header是根本原因。我得到的响应是一个长字符串,并且由于这个 header 而被压缩。我在出站网关之前添加了一个 header 过滤器以删除此 header.

    @Bean
    @Transformer(inputChannel = "channelHeaderFilterReq", outputChannel = "channelHeaderFilterRes")
    public HeaderFilter filter() {
        return new HeaderFilter("Accept-Encoding");
    }

现在一切正常..!!