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

Hey guys

I am learning and using seata recently, this is a great thing.

Component
spring-cloud-alibaba-seata:0.9.0.RELEASE

Question
I see that the seata source code contains the spring boot web dependency. **Is there a plan to support [sp

Issue Description

引入nacos后，导致服务启动失败
异常信息： Could not resolve placeholder 'project.version' in value "${project.version}"

Describe what happened (or what feature you want)

异常栈：

2020-08-05 15:47:11.844 [ERROR] [main] [org.springframework.boot.SpringApplication] @@@traceId=@@@ Application startup failed
org.springframework.beans.factory.UnsatisfiedDependencyException: Erro

Environment:

• Jib version: 2.4.0
• Build tool: Gradle 5.6.1
• OS: Windows 10 build 2004

Description of the issue:
Not specifying the username in --image parameter results in 401 unauthorized

Steps to reproduce:

Note: I have fixed the issue by adding username before image name , this is more of an en

The example nginx configuration in the Deploying Falcon on Linux with NGINX and uWSGI article could probably be improved to include https configuration and redirect of http to https, since I believe it's the most common configuration now.

Maybe we could use a configuration from this great [Mozilla site](https://ssl-config

Since #1986 was merged one can simply start full backstage instance by just starting the backend, which is imo very sweet 😃
But, some backend plugins that are missing 404 handler of their own are now showing 404 of the frontend, which is not desirable behavior in the most of the cases.
As a starting point - plugin-proxy-backend should really just give 404 of its own if something isn't there o

/area operator

Ops are not loving the idea of giving dapr-operator cluster-admin permissions. Is this really necessary and if so, what is it necessary for (i.e. what operations does it have to do where more restrictive permissions would not suffice)?

Thanks!

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

**Do you want to request a feature or report a bug?

Feature?

What is the current behavior?
Session object ACLs require both the key and the api_id field of the ACL definition to match.

If they mismatch the API does not throw an error.

What is the expected behavior?

The Gateway API should report the discrepancy to stop the token from being generated.