v1.3.3 之后，慢请求会无响应，但日志输出正常响应 200

[zze326]

[miaogaolin]

我测试了下，如果说的不对，可以提出来： api 文件中的超时配置，决定的是局部请求 yaml 配置文件中 Timeout 值决定的是全局，而这个值默认 3s ，所有要保证 yaml 文件中的Timeout （单位毫秒）配置大于 @server 中的超时配置

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

I tested it, and if it's wrong, you can put it up: The timeout configuration in the api file determines the local request The Timeout value in the conf configuration file determines the global value, and this value defaults to 3s, so make sure that the Timeout (in milliseconds) configuration in conf is greater than the timeout configuration in @server

[zze326]

我测试了下，如果说的不对，可以提出来： api 文件中的超时配置，决定的是局部请求 yaml 配置文件中 Timeout 值决定的是全局，而这个值默认 3s ，所有要保证 yaml 文件中的Timeout （单位毫秒）配置大于 @server 中的超时配置

不合理，应该是允许局部（@server）覆盖全局（yaml），而且输出的响应日志和实际响应报文也不一致，且 v1.3.3（含） 之前没有这个问题，所以我认为这是一个 bug

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

I tested it, if it is wrong, you can put it forward: The timeout configuration in the api file determines the local request The Timeout value in the yaml configuration file determines the global value, and this value defaults to 3s, all must be guaranteed in the yaml file The Timeout (in milliseconds) configuration is greater than the timeout configuration in @server! image

Unreasonable, it should allow the local (@server) to overwrite the global (yaml), and the output response log is inconsistent with the actual response message, and there is no such problem before v1.3.3 (inclusive), so I think this is a bug

[smithyj]

我测试了下，如果说的不对，可以提出来： api 文件中的超时配置，决定的是局部请求 yaml 配置文件中 Timeout 值决定的是全局，而这个值默认 3s ，所有要保证 yaml 文件中的Timeout （单位毫秒）配置大于 @server 中的超时配置

不合理，应该是允许局部（@server）覆盖全局（yaml），而且输出的响应日志和实际响应报文也不一致，且 v1.3.3（含） 之前没有这个问题，所以我认为这是一个 bug

赞同这个说法，局部的应该覆盖全局

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

I tested it, if it is wrong, you can put it forward: The timeout configuration in the api file determines the local request The Timeout value in the yaml configuration file determines the global value, and this value defaults to 3s, all the yaml files must be guaranteed The Timeout (in milliseconds) configuration in @server is greater than the timeout configuration in @server! image

Unreasonable, it should allow the local (@server) to overwrite the global (yaml), and the output response log is inconsistent with the actual response message, and there is no such problem before v1.3.3 (inclusive), so I think this is a bug

Agree with this statement, the local should override the global

[kevwan]

Will work on it.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.