Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom-host in header overwrites custom_host in config.providers.custom_host in fallback mode #431

Open
villageFlower opened this issue Jul 7, 2024 · 0 comments
Labels
bug Something isn't working triage

Comments

@villageFlower
Copy link

What Happened?

Hi, the custom_host in config providers does not work when given x-portkey-custom-host in request headers. All fallback providers tends to use the one given in x-portkey-custom-host instead of the one in x-portkey-config. Thank you for the project and feel free to approch me for more details

What Should Have Happened?

No response

Relevant Code Snippet

below is the demo config file. Eventhough custom_host is specified. It still goes to x-portkey-custom-host
{ "strategy": { "mode": "fallback" }, "targets": [ { "provider": "openai", "api_key": "OPENAI_API_KEY_FROM_HOST_2","custom_host":"HOST_1" }, { "provider": "openai", "api_key": "OPENAI_API_KEY_FROM_HOST_2","custom_host":"HOST_2" } ] }

Your Twitter/LinkedIn

No response

@villageFlower villageFlower added the bug Something isn't working label Jul 7, 2024
@github-actions github-actions bot added the triage label Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

1 participant