We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@hellosean1025 你好,我注意到最新的一个提交 fix: get 请求会带上 content-type bug 对于get请求传入的content-type做了delete过滤处理,我想了解下如果不做这个过滤,可能会导致什么样的bug出现呢?
我知道在http标准中get请求是不存在content-type字段的,但实际业务当中不免有些不太合理的判断逻辑封装,比如后端接口在框架层去校验所有请求(不论get/post)的content-type,这样一来插件的这个过滤逻辑反而会导致无法测通接口。
我个人的想法,对于代理工具而言,是否应该完全透明化,把所有参数配置传入的决定权都交给用户,而不是主动去“纠正”用户“不太合理”的传入?
The text was updated successfully, but these errors were encountered:
部分服务器解析会出现异常
Sorry, something went wrong.
No branches or pull requests
@hellosean1025 你好,我注意到最新的一个提交 fix: get 请求会带上 content-type bug 对于get请求传入的content-type做了delete过滤处理,我想了解下如果不做这个过滤,可能会导致什么样的bug出现呢?
我知道在http标准中get请求是不存在content-type字段的,但实际业务当中不免有些不太合理的判断逻辑封装,比如后端接口在框架层去校验所有请求(不论get/post)的content-type,这样一来插件的这个过滤逻辑反而会导致无法测通接口。
我个人的想法,对于代理工具而言,是否应该完全透明化,把所有参数配置传入的决定权都交给用户,而不是主动去“纠正”用户“不太合理”的传入?
The text was updated successfully, but these errors were encountered: