multiple origins

[LukaszHem]

Feature request

Using CORS_ALLOW_ORIGIN I was able to set single origin to avoid CORS issues.
CORS_ALLOW_ORIGIN=123.45.67.8:1234
How do I set it up for multiple origins?

Motivation

I want to use TGI to from multiple origins.
I could set up proxy between TGI and my TGI clients, but that looks like a hacky solution. It gets even hackier when you need to use streaming (which I need to do).
Additionally proxy solution will cause problems, when you try to use TGI with agents.

Your contribution

Maybe we could pass list of origins separated by comma
CORS_ALLOW_ORIGIN=origin1,origin2
CORS_ALLOW_ORIGIN=123.45.67.8:1234,123.45.67.8:1243

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[LukaszHem]

Up to avoid stale.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[LukaszHem]

Up to avoid stale.

[LukaszHem]

According to this: docker/compose#4249 docker compose is scheduled to support array of strings in the future. But for now the only way to achieve passing multiple origins is if TGI would split passed string variable and convert value to array of strings. You can see current cors_allow_origin value in container logs when TGI container is starting:

// docker compose
CORS_ALLOW_ORIGIN=123.45.67.8:1234,123.45.67.8:1243
// current TGI logs
cors_allow_origin: [
        "123.45.67.8:1234,123.45.67.8:1243",
],
// expected TGI logs
cors_allow_origin: [
        "123.45.67.8:1234",
        "123.45.67.8:1243"
],

Value passed by docker is internally already an array. So either it is already possible and not documented or require minimal change.

[srjchauhan]

I need the exact same feature. Can you please include this in roadmap