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
whistle有个默认的超时时间(36s),在调试慢速接口时,请求会被干掉,在浏览器上看到请求失败,并且返回内容为空。但是在whistle的抓包详情里有超时信息。即使这样,如果只看chrome network和接口日志的话,很难发现请求失败是由于whistle的超时机制。
建议是否能将whistle里的超时信息以合适的方式让chrome 的network里也能看到?
whistle versoin: 1.5.8
chrome console:
chrome network response/preview:
whistle response:
The text was updated successfully, but these errors were encountered:
试了一下配置 disable://timeout 请求还是在1min的时候返回错误,这时chrome的response里能看到whistle的信息了:
调试的这个接口比较奇葩,居然要2min左右,也是醉了。。。
Sorry, something went wrong.
默认超时还是有必要,不然可能会导致某些域名的请求连接无法释放而不断累积,最后导致该域名的请求无法访问。
重新安装下whistle,新版本把默认超时改为 1min 与IE浏览器的默认超时时间同步,如果需要更长的超时时间可以设置 disable://timeout 或通过启动参数 w2 restart -t 600000 修改默认超时时间(单位:毫秒)
1min
disable://timeout
w2 restart -t 600000
No branches or pull requests
whistle有个默认的超时时间(36s),在调试慢速接口时,请求会被干掉,在浏览器上看到请求失败,并且返回内容为空。但是在whistle的抓包详情里有超时信息。即使这样,如果只看chrome network和接口日志的话,很难发现请求失败是由于whistle的超时机制。
建议是否能将whistle里的超时信息以合适的方式让chrome 的network里也能看到?
whistle versoin: 1.5.8
chrome console:

chrome network response/preview:

whistle response:

The text was updated successfully, but these errors were encountered: