4

当我使用 aFeignClient时，它设置为Content-Typetoapplication/x-www-form-urlencoded而不是application/json;charset=UTF-8.

如果我使用 aRestTemplate发送相同的消息，则消息头Content-Type正确设置为application/json;charset=UTF-8.

FeignClient和都RestTemplate用于Eureka服务发现，我通过调试服务器接收到的 HTTP 消息发现了这个问题。

服务器端的控制器如下所示：

@RestController
@RequestMapping("/site/alarm")
public class SiteAlarmController {
    @RequestMapping(method = RequestMethod.POST)
    @ResponseBody
    public ResponseEntity<RaiseAlarmResponseDto> raiseAlarm(@RequestBody RaiseSiteAlarmRequestDto requestDto) {
        ...
    }

我FeignClient在调用警报的服务中的界面如下所示：

@FeignClient("alarm-service")
public interface AlarmFeignService {
    @RequestMapping(method = RequestMethod.POST, value = "/site/alarm")
    RaiseAlarmResponseDto raiseAlarm(@RequestBody RaiseSiteAlarmRequestDto requestDto);
}

来自的 HTTP 消息标头FeignClient是：

Accept: */*
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.7.0_60
Host: smit005s-MacBook-Pro.local:9120
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded
Content-Length: 323

警报服务不喜欢Content-Type并抛出以下异常：

2015-04-22 12:12:28.580 thread="qtp1774842986-25" class="org.eclipse.jetty.servlet.ServletHandler" level="WARN" 
org.springframework.web.util.NestedServletException: Request processing failed; nested exception is feign.FeignException: status 415 reading AlarmFeignService#raiseAlarm(RaiseSiteAlarmRequestDto); content:
{"timestamp":1429701148576,"status":415,"error":"Unsupported Media Type","exception":"org.springframework.web.HttpMediaTypeNotSupportedException","message":"Unsupported Media Type","path":"/site/alarm"}
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:978) ~[spring-webmvc-4.1.5.RELEASE.jar:4.1.5.RELEASE]
    at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:857) ~[spring-webmvc-4.1.5.RELEASE.jar:4.1.5.RELEASE]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:618) ~[tomcat-embed-core-8.0.20.jar:8.0.20]
    ...
    ... /* commented rest of stack out */
    ...

如果我将客户端代码更改为使用RestTemplate如下：

@Service
public class AlarmService {
    @Autowired
    private RestTemplate restTemplate;
...
    public void send(RaiseSiteAlarmRequestDto alarm) {
        RaiseAlarmResponseDto result = restTemplate.postForObject("http://alarm-service/site/alarm", 
            raiseSiteAlarmRequestDto, RaiseAlarmResponseDto.class);
    }
}

它与 一起工作RestTemplate，alarm-service接收消息并成功处理它。发送的消息头RestTemplate是：

Accept: application/json, application/*+json
Content-Type: application/json;charset=UTF-8
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Java/1.7.0_60
Host: smit005s-MacBook-Pro.local:9120
Connection: keep-alive
Content-Length: 323
4

1 回答 1

16

答案是按照@spencergibb 的建议去做；使用接口注释中的consumes指令。这个Spring/Netflix 文档也有一个例子。@RequestMappingFeignClient

例如，@FeignClient客户端中的接口声明现在是：

@FeignClient("alarm-service")
public interface AlarmFeignService {
    @RequestMapping(method = RequestMethod.POST, value = "/site/alarm", consumes = "application/json"))
    RaiseAlarmResponseDto raiseAlarm(RaiseSiteAlarmRequestDto requestDto);
}

请注意，这仅在客户端是必需的，服务器端控制器不需要进行此更改。

如果在默认情况下这样做会很好@FeignClient，然后它将与RestTemplate服务器端控制器@RequestMapping注释一致。也许这可以在未来的spring-cloud.

于 2015-04-24T10:47:10.227 回答