API网关错误码表(VPC实例)
本文主要介绍VPC实例的API网关错误码表。
本章节的错误代码表适用于VPC共享实例/Serverless实例
和VPC专享实例
。
当客户端收到的应答中
X-Ca-Error-Code
头不为空,表示应答码由API网关产生,错误码由一个6位长度的字符描述,请参考下表,而X-Ca-Error-Message
表示错误的应答信息,用于描述该场景下更详细的一些错误信息。如果
X-Ca-Error-Code
头为空,则表示这个HTTP应答码由后端服务产生,API网关透传了来自后端的错误信息。
API网关错误码表
错误代码 | HTTP状态码 | Message | 描述 |
I400HD | 400 | Invalid Header `${HeaderName}` ${Reason} | HTTP请求头非法 |
I400MH | 400 | Header `${HeaderName}` is Required | 缺少HTTP请求头 |
I400BD | 400 | Invalid Body: ${Reason} | HTTP请求包体非法 |
I400PA | 400 | Invalid Request Path `${Reason}` | HTTP请求路径非法 |
I405UM | 405 | Unsupported Method `${Reason}` | 不支持的HTTP请求方法 |
I400RU | 400 | Invalid Request Uri `${Reason}` | HTTP请求URL非法 |
I403PT | 403 | Invalid protocol ${Protocol} unsupported | 使用了API配置中不支持的协议,请检查API配置的协议 |
I413RL | 413 | Request body too Large | 请求包体过长,相关限制参考使用限制 |
I413UL | 413 | Request URL too Large | 请求URL过长,相关限制参考使用限制 |
I400CT | 400 | Invalid Content-Type: `${Reason}` | 非法的`Content-Type` |
I404DO | 404 | Invalid Domain `${DomainName}` | 未知的请求域名,请使用绑定的域名进行调用 |
I410GG | 410 | Group's instance invalid | 请求了非法的实例,分组可能已经不属于当前实例 |
I400SG | 400 | Invalid Stage | 请求了未知的环境 |
I404NF | 404 | API not found ${Reason} | 根据请求的`Path`,`Method`在当前的环境中未找到API,请参考I404NF错误码排查 |
X400PM | 400 | Invalid plugin meta ${PluginName} ${Reason} | 插件元数据非法 |
X500ED | 500 | Expired api definition | 过期的老版本元数据已经不被新版本API网关支持,需要提交工单修改老版本元数据 |
X500AM | 500 | Invalid Api Meta, try deploy again or contact us via ticket | 保存的元数据定义格式错误,需要提交工单修复 |
X403DG | 403 | Bad Domain or Group: ${Reason} | 分组数据非法 |
B451DO | 451 | Unavailable Domain for Legal Reasons | 域名因法律法规问题被禁 |
B451GO | 451 | Unavailable Group for Legal Reasons | 分组因法律法规问题被禁 |
B403OD | 403 | Provider Account Overdue | API提供方欠费,若是云市场购买的API,请联系服务商处理 |
A401AC | 401 | Invalid AppCode ${Reason} | 当使用AppCode模式授权时,未找到AppCode,请核实App是否授权,AppCode是否有误 |
A400IK | 400 | Invalid AppKey | 当使用`Key/Secret`签名授权时,未找到AppKey |
A403IS | 403 | Invalid Signature, Server StringToSign:`${StringToSign}` | 签名不匹配,排查请参考返回A403IS错误码 |
A403EP | 403 | App authorization expired | 授权已过期,请重新授权 |
A403PR | 403 | Plugin Authorization Needed | 需要插件授权 |
A400MA | 400 | Need authorization, `X-Ca-Key` or `Authorization: APPCODE ...` is required | 需要使用`Key/Secret`签名授权或`AppCode`授权 |
I400I5 | 400 | Invalid Content-MD5 ${Reason} | 不匹配的`Content-MD5` |
I400NC | 400 | X-Ca-Nonce is required | 当设置了`使用X-Ca-Nonce防重放`选项时,必须提供`X-Ca-Nonce`头 |
S403NU | 403 | Nonce Used | 检测到请求重放,请求的`X-Ca-Nonce`头重复 |
S403TE | 403 | X-Ca-Timestamp is expired | `X-Ca-Timestamp`头中提供的时间戳已过期,时间戳有效期15分钟 |
I400MP | 400 | Parameter `${ParameterName}` is required | API中配置的必填参数未传值 |
I400IP | 400 | Invalid parameter `${ParameterName}` ${Reason} | API中配置的参数值非法 |
I400JR | 400 | JWT required | 未找到JWT参数 |
S403JI | 403 | Claim `jti` is required when `preventJtiReplay:true` | 当在`JWT授权插件`中配置了防重放功能时,请求未提供有效的`jti` |
A403SV | 403 | Claim `jti` in JWT is used | 当在`JWT授权插件`中配置了防重放功能时,请求提供的`jti`已被使用 |
I400JD | 400 | JWT Deserialize Failed: `${Token}` | 请求中提供的`JWT`解析失败 |
A403JT | 403 | Invalid JWT: ${Reason} | 请求中提供的`JWT`非法 |
A403JK | 403 | No matching JWK, `${kid}` not found | 请求`JWT`中的`kid`没有匹配的`JWK` |
A403JE | 403 | JWT is expired at `${Date}` | 请求中提供的`JWT`已过期 |
I400JP | 400 | Invalid JWT plugin config: ${JWT} | `JWT授权`插件配置错误 |
A403OL | 403 | OAuth2 Login failed: ${Reason} | |
A403OU | 403 | OAuth2 Get User Info failed: ${Reason} | |
A401OT | 401 | Invalid OAuth2 Access Token | |
A401OM | 401 | OAuth2 Access Token is required | |
T429ID | 429 | Throttled by INNER DOMAIN Flow Control, ${Domain} is a test domain, only 1000 requests per day | 当使用默认二级域名访问时,限制1000次/天,(海外Region及中国香港限制100次/天),请绑定正式域名以解除这个限制 |
T429IN | 429 | Throttled by INSTANCE Flow Control | 触发当前实例的流控限制,请升级实例规格 |
T429GR | 429 | Throttled by GROUP Flow Control | 触发当前分组的流控限制,请升级实例规格 |
T429PA | 429 | Throttled by API Flow Control | 触发插件上的默认API流控 |
T429PR | 429 | Throttled by PLUGIN Flow Control | 触发插件的特殊流控 |
T429SR | 429 | Throttled by SERVER Flow Control | |
T429MR | 429 | Too Many Requests, throttle by `${Description}` | |
A403IP | 403 | Access denied by IP Control Policy | 被`IP访问控制插件`阻止访问 |
A403IN | 403 | Access from internet is disabled ${Reason} | `API`或`API分组`禁止从公网访问,请从内网调用,文档参考私网调用API |
A403VN | 403 | Access from invalid VPC is disabled | 来源VPC被阻止 |
A403AC | 403 | Access Control Forbidden by ${RuleName} | 被`授权控制`插件阻止 |
A403CO | 403 | Cross origin resource forbidden ${Domain} | 被CORS策略阻止访问 |
I404CO | 404 | Cross origin resource not found ${Method} - ${Path} | 根据CORS预检请求中的Path与Method,无法找到API定义 |
I404CH | 404 | Content not cached, with `Cache-Control:only-if-cached` | |
I404NR | 404 | ${Resource} not found | |
I404SR | 404 | Stage route missing: ${Reason} | |
B403MO | 403 | Api Market Subscription overdue | API提供商欠费,请联系服务商处理 |
B403MQ | 403 | Api Market Subscription quota exhausted | 购买的云市场API配额已耗尽,请续费次数 |
B403ME | 403 | Api Market Subscription expired | API订购关系已过期,请重新订购 |
B403MI | 403 | Api Market Subscription invalid | API市场订购关系非法 |
D504RE | 504 | Backend domain `${Domain}` resolve failed | 后端域名解析失败,请核实后端域名解析 |
D504IL | 504 | Backend domain `${Domain}` resolve to illegal address `${Address}` | 后端域名解析结果非法 |
D504CO | 504 | Backend service connect failed `${Reason}` | 后端连接失败,请检查安全组、后端服务器启动状态、或防火墙配置,排查可参考D504CO错误码排查 |
504 | Backend service connect failed `Connection lease request time out` | API网关实例后端连接池不够用导致的后端连接失败,请升级实例规格 | |
D504CS | 504 | Backend http ssl connect failed `${Reason}` | 后端HTTPS连接失败,请检查后端配置的协议与端口是否匹配 |
D504TO | 504 | Backend service request timeout | API网关请求后端超时,请调整后端超时时间或提高后端服务响应速度 |
X504VE | 504 | Backend service vpc mapped failed | 后端VPC映射错误 |
D503BB | 503 | Backend circuit breaker busy | API被断路器阻止 |
D503CB | 503 | Backend circuit breaker open, ${Reason} | API处于熔断/断路器开状态,请检查后端性能 |
I508LD | 508 | Loop Detected | 检测到环回调用 |
I404DD | 404 | Device id ${DeviceId} not found | 当使用WebSocket双向通信调用时,DeviceId未找到 |
A403FC | 403 | Function Compute AssumeRole failed ${RequestId}:${Reason} | 后端是函数计算时授权错误 |
D502FC | 502 | Function Compute response invalid: ${Reason} | 后端是函数计算时,来自后端的应答非法 |
N502RE | 502 | Send Response IO Exception: ${Reason} | 发送应答给客户端时报错,常见于客户端提前关闭连接或网络错误 |
X500ER | 500 | Service Internal Error | 服务器内部错误,请提交工单联系工作人员 |
X503BZ | 503 | Service Busy | API网关服务忙,请稍后再试 |
X504TO | 504 | Service timeout | API网关处理超时,请提交工单联系工作人员 |
部分错误代码可能随着升级或新功能的加入而改变。