Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13
Internet says it should return 204:
Internet changed its mind since 2018 https://
The #1718 modified how static files are handled to prevent directory traversal. On that PR, some unit test were added to echo_test.go, but those test were not implemented for the Static Middleware (static_test.go)
The idea of this issue is to implement the missing test on the Static Middleware in relation to TestEchoStatic tests.
Is your feature request related to a problem? Please describe in details
increase rm-datasource module test coverage
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.
Add any other context or screenshots about the feature request here.
Type: feature request
gateway flow limit by error code instead of Throwable exception
对于 API gateway 目前不支持针对 4xx、5xx 等状态码记为错误（仅针对抛出异常记录错误）。希望可以针对 5xx 等状态码也记录为错误，这样就可以进行异常熔断降级了。
Is your feature request related to a problem? Please describe.
It is idiomatic for JWTs to be accepted using a header format of Authorization: Bearer <JWT> (see jwt.io introduction.) In general, in history, the RFCs surrounding the authorization header have taken care to specify the mode of Authorization as the first part of the header value (e.g. Basic, Di
/area runtime
/area operator
/area placement
/area docs
/area test-and-release
0.1.x
0.2.x
Output of git describe --dirty
E
| Q | A |
|---|---|
| Bug report? | yes |
| Feature request? | no |
| Swoft version | 2.0.6 |
| Swoole version | 4.5.2 |
| PHP version | 7.2.29 |
| Runtime environment | Docker etc. |
Describe the bug
在框架里使用Redis::scan 函数时获取不到数据,而原生文件可以
Screenshots
我需要
可我在hyperf中不知道该如何使用write
Type: feature request
chaosblade是一款覆盖面很广的故障注入测试工具，因此我希望引入此软件对 K8s Paas平台进行测试，但是发现只能针对特定的pod进行故障注入（delete pod或者pod cpu负载等），没有其他针对Paas 的chaos工具（Powerfulseal、Chaos-mesh等）拥有在规定时间内随机等delete 规定分区下的po
Add a description, image, and links to the microservice topic page so that developers can more easily learn about it.
To associate your repository with the microservice topic, visit your repo's landing page and select "manage topics."
