feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for

响叮当！

已于 2024-07-24 21:36:33 修改

阅读量5.4k

点赞数 6

CC 4.0 BY-SA版权

文章标签： java 开发语言

于 2024-07-22 17:28:32 首次发布

本文链接：https://blog.csdn.net/m0_52767002/article/details/140603669

一、报错

Could not extract response: no suitable HttpMessageConverter found for response type [xxx] and content type [application/octet-stream] 

feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [xxx] and content type [application/octet-stream]

解释一下：就是Feign自带的转换器中，无法把[class XXX]转换成content type [XXX;XXX]

在使用SpringCloud FeignClient的时候，经常的情况是我们希望返回的是一个application/json类型的返回，
当返回是[application/octet-stream]类型或者其他自带转换器中没有的类型时，feign调用就会解析错误。

二、具体源码分析

（1）在 Springboot 默认处理器为 `MappingJackson2HttpMessageConverter`

用于将 Java 对象转换为 JSON 格式。

但是MappingJackson2HttpMessageConverter，只支持"application/json"类型；因此springboot没有找到合适的HttpMessageConverter,于是报出了上面的异常。

（2）feign默认的Decoder为SpringDecoder

最低0.47元/天解锁文章

200万优质内容无限畅学

确定要放弃本次机会？

福利倒计时

: :

立减 ¥

普通VIP年卡可用

立即使用

响叮当！

关注关注

6
点赞
踩
10

收藏

觉得还不错? 一键收藏
0
评论
分享

复制链接

分享到 QQ

分享到新浪微博

扫一扫
举报

举报

Fegin 错误 Could not extract response: no suitable HttpMessageConverter found for XXX

大鹏小站的博客

11-27

7369

问题：这两天用Fegin 调用其他小组的下载接口报错 feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [class com.XXX…manager.dto.HaloResponse] and content type [application/octet-stream;charset=UTF-8] 原因：对方返回的结果用pos

Feign 解码异常处理：解决 No Suitable HttpMessageConverter 问题

最新发布

wxd0116的博客

04-27

2850

需求：服务端返回text/plain类型的 JSON 字符串，需转换为对象。@Override> clazz) {// 支持所有可通过 Jackson 转换的类型@Overridetry {// 读取文本内容// 使用 Jackson 将文本转为 JSON 对象@Override// 若需支持请求体写入（可选实现）@Bean// 或 TextPlainStringConverterFeign 的明确响应格式与类型：确保服务端返回内容与一致。

参与评论您还未登录，请先登录后发表或查看评论

feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found

Ciel_Y的博客

02-03

8558

feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found

Could not extract response: no suitable HttpMessageConverter

阿呆的专栏

02-26

1万+

版本：spring-cloud-openfeign-core-2.1.1.RELEASE.jar，spring-webmvc-5.1.14.RELEASE.jar，jetty-server-9.4.41.v20210516.jar，tomcat-embed-core-9.0.48.jar。

【OpenFeign报错排查】Could not extract response: no suitable HttpMessageConverter found for response type

Bankcary的博客

02-27

6614

起因：当调用get方法时，报错Could not extract response: no suitable HttpMessageConverter found for response type，解释就是无法序列化成Result，也就是返回值根本就不是一个json或者不是你需要的Result对象，通过对get2和get3方法的验证，发现get3方法返回值是一个500异常报错（也可以通过开启feign日志排查）

针对feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found

m0_54101192的博客

06-12

840

没有摘要

【feign】feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter

ooooooooooooooxiaosu的博客

06-27

7943

feign jar包调用

怎么解决feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response typ

10-27

feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [class com.chinahrt.gp6.system.sharevo.UserBaseDto] and content type [text/html;...

feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response typ

10-27

feign.codec.DecodeException是一个Feign客户端调用远程服务时可能会出现的异常。它通常是由于无法将响应转换为期望的类型而引起的。在这个特定的错误中，它表示没有找到适合响应类型的HttpMessageConverter。这可能...

Could not extract response: no suitable HttpMessageConverter found for content type [text/html]

热门推荐

小草莓的博客

02-13

1万+

}

Could not extract response: no suitable HttpMessageConverter found for response type

u012609879的博客

08-20

5926

Could not extract response: no suitable HttpMessageConverter found for response type [class com.XXX] and content type [text/plain] 1. 报错 feign.codec.DecodeException: Could not extract response: no sui...

解决:Could not extract response: no suitable HttpMessageConverter found for content type [xxx]

菜鸡的博客

04-27

1万+

解决:Could not extract response: no suitable HttpMessageConverter found for content type [xxx]

Could not extract response: no suitable HttpMessageConverter found for response type...and content

懒虫的博客

10-07

1467

今天前端接受到后台代码报错Could not extract response: no suitable HttpMessageConverter found for response type […] and content type [text/html]，我们一直都是用的json数据来传输，所以不存在content type传错了。原因其实是因为使用feign调的后台服务，但是后台服务未启，返回的是一段html格式的错误信息。

SysException:feign.codec.DecodeException:Could not extract response:no suitable HttpMessageConverter

yzg0885的博客

05-17

455

SysException:feign.codec.DecodeException:Could not extract response:no suitable HttpMessageConverter

feign 服务间调用异常，feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConver

yzhao66的博客

04-11

7523

feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [] and content type [text/html;charset=UTF-8] 这是由于微服务添加spring-security-oauth2-autoconfigure导致调用微服务401unauthorised try { String to

OpenFeign远程调用报错：Could not extract response: no suitable HttpMessageConverter found for response type

你今天真好看呀

04-19

6597

远程调用的项目使用PHP写的，因此我只能通过页面的请求参数封装请求Vo，然后调用PHP项目的接口封装响应类。 ① 请求体：Feign接口中请求体的字段要比调用的PHP项目中接口的请求体字段少 @Data public class AssetListQo { @JsonProperty(value = "time_range") private String timeRange; @JsonProperty(value = "branch_id") private Strin

OpenFeign Could not extract response: no suitable HttpMessageConverter found for response type 问题解决

旭东怪的博客

04-19

4368

问题描述： feign.codec.DecodeException: Could not extract response: no suitable HttpMessageConverter found for response type [com.common.util.Result<com.entity.User>] and content type [text/html] 问题分析： 1、调用接口地址与被调用接口地址不一致，导致报错。被调用的接口： @RestControll

【Feign请求头丢失问题】no suitable HttpMessageConverter found for response type

weixin_45654405的博客

09-09

1万+

HttpMessageConverter 失败的原因是：在项目中使用了一个拦截器拦截请求，部分接口需要登陆才能访问，否则返回一个text/html格式的响应，导致远程服务解析响应失败。登陆失败的原因是：Feign发起远程调用的时候会重新生成一个新的请求，带来的问题就是不会携带原来请求的cookie，导致调用需要登陆的远程接口时会失败。解决方法是配置一个Feign的拦截器，在发送请求的时候带上原请求的cookie。