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

Simple Introduction

Apollo's document can view on website https://ctripcorp.github.io/apollo

It's content under git repository directory docs.

Directory docs/zh save Chinese document.

Directory docs/en save English document.

The document structure use https://docsify.js.org/#/ (More detail in pull request #3433)

Someone can add English document now.

Example

Chin

Wiki 文档

配置的优先级
文档中写到“优先级关系是:A < B < C”，存在歧义容易造成混淆，建议修改。
应使用更为确切的说法，优先级的定语是“高和低”而不是“大和小”，并不一定所有读者都有“优先级数值小即优先级高”的认知
同时，例子中使用 A、B 和 C 亦没有体现出数值的概念，进一步加深了读者的疑惑。
如：“优先级大”、“优先级数值小”和“优先级高”，是否应选择“优先级高”才是最清晰的表达方式？

Beta release: Grayscale release can not select client IP needs to be filled in manually, hope to add support to select IP directly from the connected client
Beta发布: 灰度发布不能选择客户端ip 需要手动填写，希望增加支持从已连接的客户端直接选择ip

Expected Behavior

OIDC login should use standard scopes as defined by the OIDC spec.

Current Behavior

default is concatenated to the list of

I need to define env-vars in the sidecar runtime-env in order to make SQS calls go via a http-proxy.
This is not possible today.
it could have syntax of dapr.io/env/varname=value and be placed in the annotations.

/area runtime

Describe the feature

Allows for controlling env-vars of the sidecar.

Release Note

Implement + update docs.

Background

目前使用qiankun2.x的版本，业务提出需求在发布新的版本时候，期望可以不刷新页面（主应用暂时不考虑）进行该系统的热重载。类似于pc端的热更新，期望qiankun可以导出unload方法，完全销毁app的生命周期，业务系统再次将其重载。

Proposal

1. 翻看源码发现不能热更新的原因是因为import-html-entry中缓存了 embedHTMLCache
2. qiankun在importEntry时，如果已经获取过html资源，每次获取的都是内存中的html，以至于script & style也是缓存的
3. 我的解决方案是，在import-html-entry中导出根据app去清除缓存的钩子函数
4. 在qiankun中包裹其方法，根据single-spa的appStatus进行卸载应用

Grep the code for "deprecated", etc. and remove relevant code/interfaces. Be sure to include news fragments for each change.

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna