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://

rocket mq can set the maxReconsumeTimes param,when use the stream cloud rocketmq, there is no config for this, would it surport ont the future?

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

Describe the bug
See screenshot. Should be don't not don't

To Reproduce
Steps to reproduce the behavior:

1. Install latest 4.0 windows client
2. Add cluster
3. Go to cluster settings
4. Read text for "accessible Napespaces"

Expected behavior
Escaped cor

API documentation for nodejs client for hydra returns a 404

The link mentioned in the documentation: https://github.com/ory/hydra/blob/master/sdk/js/swagger/README.md

Description

Adding Indonesian translation of Readme.md and contributing.md

Con

Currently the service profile generation from proto/swagger requires that you have access to the k8s cluster that has Linkerd running.

The only reason for this is that currently the cluster domain is fetched from the Linkerd installation on the cluster.

I propose that the profile command be updated to support the --ignore-cluster flag
I also propose that there should be a flag `--cluste

Steps to reproduce

1. Create a universe with encryption at-rest enabled
2. Edit universe > Notice KMS config is currently displayed
3. Refresh the page > KMs config is cleared and shows "Select Configuration"

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

So far we don't enable the SNI extension when communicating with upstream. If upstream server depends on SNI to select proper certificate, then the TLS/SSL handshaking will fail. So we should carry the SNI extension.

Nginx has a directive named proxy_ssl_server_name.

Syntax: proxy_ssl_server_name on | off;
proxy_ssl_server_name 

What would you like to be added/modified:

To improve project stability, we need more tests to cover corner cases.
And the code coverage is around 50% currently, we need to add more tests to improve it.

To improve case coverage, we may need a list of cases to track the work.
For code coverage, simply check bef

There is no e2e test and documents for external network delay and partition now 🤦 .

The e2e test could be found in /test/e2e/chaos/basic.go. Reading other tests in that file could help accomplish this issue.

Example for extern network delay:

apiVersion: chaos-mesh.org/v1alpha1
kind: NetworkChaos
metadata:
  name: network-netem-example
  namespace: chaos-testing
spec: