Hello,

As a result of #5621, Serverless-created buckets include a bucket policy that is supposed to deny any s3:* Action over that bucket, unless it is performed over HTTPS.

Unfortunately that Bucket policy is incomplete and still allows listing the Bucket content over insecure HTTP connection, if the Principal has permissions to perform that action.

Incorrect (current) Bucket Policy:

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:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

Why you need it?

Is your feature request related to a problem? Please describe in details
increase rm-datasource module test coverage

How it could be?

A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

Other related information

Add any other context or screenshots about the feature request here.

Issue Description

bug report

Describe what happened (or what feature you want)

当配置-Dcsp.sentinel.dashboard.server为指定地址，但这个地址会强制跳转http

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

Add a performance test that measures the time it takes Dapr to save data into a state store.

The important piece that is being tested is the processing that Dapr does before saving to the state store. This test should not benchmark the component itself.

For that purpose, a baseline test scenario would have an app that saves a 1kb payload to Redis, followed by a test app that uses Dapr to sav

使用mysql+kafka模式。用JMeter模拟1W数据2秒启动100个线程，循环100次，JMeter界面8s左右请求完毕，然后查看消费端，消费的很慢1s就三四十条左右，应该是发送端发送的慢，和这个测试基本一样 #416

我需要

可我在hyperf中不知道该如何使用write

Issue Description

Type: feature request

Describe what happened (or what feature you want)

chaosblade是一款覆盖面很广的故障注入测试工具，因此我希望引入此软件对 K8s Paas平台进行测试，但是发现只能针对特定的pod进行故障注入（delete pod或者pod cpu负载等），没有其他针对Paas 的chaos工具（Powerfulseal、Chaos-mesh等）拥有在规定时间内随机等delete 规定分区下的po