Bug when adding Origin to CORS plugin

[K-Diger]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.8.0

Current Behavior

Adding an allow entry for a new origin to a gateway service using the CORS plugin does not work properly.

If I added an Origin called "http://my-tet-domain.com" to the Origin whitelist inside the CORS Plugin, CORS for this Origin should resolve normally for all requests.

However, CORS error are occurring quite frequently, and CORS permission settings are being passed intermittently.

This phenomenon of irregular plugin application needs to be resolved.

The environment in which I use Kong Gateway is Rocky Linux, and there are no problems related to the Upstream Server or Route path.

Also, I manage this configuration information in DB Mode using PostgreSQL.

Expected Behavior

If you add origins to be allowed in the CORS Plugin, all origins should pass normally.

Failure/success should not occur irregularly like in my case.

Steps To Reproduce

1. Define Gateway Service, Routes, and Upstreams and apply CORS Plugin to the relevant settings.

2. Register a new origin in CORS Plugin.

3. Send a request to the Kong Gateway from the new registered Origin.

Anything else?

No response

[xianghai2]

Rocky Linux is not a distribution with offical support from Kong.
Refer to https://docs.konghq.com/gateway/latest/install/

[K-Diger]

Rocky Linux is not a distribution with offical support from Kong. Refer to https://docs.konghq.com/gateway/latest/install/

Kong is running as a Docker container, but is the problem still related to the OS?

[samugi]

Hi @K-Diger, to help us reproduce this issue and investigate the problem, could you share your Kong configuration where the behavior is reproduced, as a deck file? Thank you very much.