[BUG] CORS_ORIGINS failing when using docker-compose

[mateusluizfb]

Describe the bug When using a docker-compose, for some reason setting the CORS_ORIGINS like this: CORS_ORIGINS="*" doesn't work, only if you set like CORS_ORIGINS=*

To Reproduce Just run the docker-compose passing CORS_ORIGINS="*" and try to request a embeded chat from another origin.

Expected behavior To work with both CORS_ORIGINS="*" or CORS_ORIGINS=*, or any custom origin

Screenshots

Response headers using CORS_ORIGINS="*"

Response headers using CORS_ORIGINS=*

Setup

• Installation docker, using docker-compose
• Flowise Version: 1.6.0
• OS: macOS
• Browser chrome,

Additional context I've noticed that the problem persists with any custom origin when using docker, not sure if happens when running natively.

[HenryHengZJ]

ah okay, we should change the .env.example from # CORS_ORIGINS="*" to # CORS_ORIGINS=*

[jiabaow]

Hello, it looks like the problem is already fixed. Maybe this issue can be closed now.