-
Notifications
You must be signed in to change notification settings - Fork 26
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
CORS issue when using Custom (OpenAI Compatible) #158
Comments
Are you using Ollama to run the model, or are you employing another method? If you're using Ollama, you can select "Ollama" as the model, and it will handle the CORS issue automatically. However, if that's not the case, perhaps it's time for us to consider adding a CORS handling option for custom models as well. |
@glowingjade , thanks for quick reply. |
@withsmilo We'll add a CORS handling option to address this issue. Thank you for bringing this to our attention. |
@withsmilo Could you share the model you're using? It will help with implementing the feature. |
I have the same issue with https://github.com/aws-samples/bedrock-access-gateway
I’ve confirmed it works with curl. |
@rewse Thanks for reporting. I will also test for amazon bedrook. |
Confirming that I have the same issue on my side. CORS with OpenAI-compatible API endpoint. We In my case, I'm seeing the following, with API endpoints obscured:
|
Hi, I'm trying to register our customized OpenAI endpoint with Smart Composer. However, I met a CORS issue in my case.
How can I address this issue? As far as I know, Copilot for Obsidian provides a way to enable CORS in their UI. (https://www.obsidiancopilot.com/en/docs/settings#adding-custom-models)
Thanks.
The text was updated successfully, but these errors were encountered: