github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #9801] CORS error: request header field openai-beta is not allowed #6410

New Issue
Closed
opened 2026-04-12 17:57:30 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-12 17:57:30 -05:00
Owner
Copy Link

Originally created by @keadex on GitHub (Mar 16, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/9801

What is the issue?

Hi there! I'm trying to send a request to the local Ollama instance, but I encounter the following issue:

Access to fetch at 'http://localhost:11434/v1/chat/completions' from origin 'http://localhost:3000' has been blocked by CORS policy: Request header field openai-beta is not allowed by Access-Control-Allow-Headers in preflight response.

Which is caused by openai-beta request header.

Here is a snippet of code to reproduce the issue:

fetch("http://localhost:11434/v1/chat/completions", {
  method: "POST",
  headers: {
    authorization: "Bearer ollama",
    "content-type": "application/json",
    "openai-beta": "assistants=v2",
  },
  body: JSON.stringify({
    messages: [
      { role: "system", content: "You are a helpful assistant." },
      {
        role: "user",
        content: "<content>",
      },
    ],
    model: "deepseek-r1:8b",
    max_tokens: 2048,
    stream: false,
  })
})

Relevant log output

Access to fetch at 'http://localhost:11434/v1/chat/completions' from origin 'http://localhost:3000' has been blocked by CORS policy: Request header field openai-beta is not allowed by Access-Control-Allow-Headers in preflight response.

OS

Windows

GPU

Intel

CPU

Intel

Ollama version

0.6.1

Originally created by @keadex on GitHub (Mar 16, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/9801 ### What is the issue? Hi there! I'm trying to send a request to the local Ollama instance, but I encounter the following issue: ```bash Access to fetch at 'http://localhost:11434/v1/chat/completions' from origin 'http://localhost:3000' has been blocked by CORS policy: Request header field openai-beta is not allowed by Access-Control-Allow-Headers in preflight response. ``` Which is caused by `openai-beta` request header. Here is a snippet of code to reproduce the issue: ```typescript fetch("http://localhost:11434/v1/chat/completions", { method: "POST", headers: { authorization: "Bearer ollama", "content-type": "application/json", "openai-beta": "assistants=v2", }, body: JSON.stringify({ messages: [ { role: "system", content: "You are a helpful assistant." }, { role: "user", content: "<content>", }, ], model: "deepseek-r1:8b", max_tokens: 2048, stream: false, }) }) ``` ### Relevant log output ```shell Access to fetch at 'http://localhost:11434/v1/chat/completions' from origin 'http://localhost:3000' has been blocked by CORS policy: Request header field openai-beta is not allowed by Access-Control-Allow-Headers in preflight response. ``` ### OS Windows ### GPU Intel ### CPU Intel ### Ollama version 0.6.1
GiteaMirror added the bug label 2026-04-12 17:57:30 -05:00
GiteaMirror commented 2026-04-12 17:57:34 -05:00
Author
Owner
Copy Link

@ParthSareen commented on GitHub (Mar 17, 2025):

Hey @keadex is there a reason for using the beta completions and not regular? We mainly have compatibility for: https://platform.openai.com/docs/api-reference/chat/create

<!-- gh-comment-id:2730513287 --> @ParthSareen commented on GitHub (Mar 17, 2025): Hey @keadex is there a reason for using the beta completions and not regular? We mainly have compatibility for: https://platform.openai.com/docs/api-reference/chat/create
GiteaMirror commented 2026-04-12 17:57:36 -05:00
Author
Owner
Copy Link

@keadex commented on GitHub (Mar 17, 2025):

Hi @ParthSareen, that header is injected by the async-openai Rust crate, so there are no ways to change it.
Disabling the CORS checks resolves the issue. It seems it's a matter of allowing that header.

<!-- gh-comment-id:2731163425 --> @keadex commented on GitHub (Mar 17, 2025): Hi @ParthSareen, that header is injected by the [async-openai](https://github.com/64bit/async-openai) Rust crate, so there are no ways to change it. Disabling the CORS checks resolves the issue. It seems it's a matter of allowing that header.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#6410
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?