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?

Describe the bug
![image](https://user-images.githubusercontent.com/20513615/102055733-431

Expected Behavior

When hovering over headings on the microsite (https://backstage.io), there should appear a little anchor link to the left. This is how it looks in GitHub when rendering the same page:

![Screenshot 2020-12-14 at 13 19 52](https://user-images.githubusercontent.com/3097461/102080864-81520600-3e0f-11eb-8d

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

0.1.x
0.2.x
Output of git describe --dirty

Expected Behavior

E

The 3.0 ASGI implementation already affords long-polling, but it would be useful to provide a recipe to demonstrate the pattern in the context of a Falcon app.

Also, for the sake of efficiency, we may want to provide a req.wait_disconnect() or similar method that can be executed in a background task within a responder. The responder could then use this in order to detect if it should abandon

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进行卸载应用

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