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

[GH-ISSUE #10126] Issue with HTTP Status "100 ContinueHTTP/1.1 200 OK" When Sending List Input to 'POST /api/embed' Endpoint #32405

New Issue
Closed
opened 2026-04-22 13:37:22 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-22 13:37:22 -05:00
Owner
Copy Link

Originally created by @dev-quentin on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10126

What is the issue?

When sending a list input to the POST /api/embed endpoint, we encounter an issue where the response contains two HTTP statuses: "100 Continue" and "HTTP/1.1 200 OK". Here is an example of the response received:

HTTP/1.1 100 Continue

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Date: Fri, 04 Apr 2025 12:25:29 GMT
Transfer-Encoding: chunked

{"model":"nomic-embed-text:latest","embeddings": [[...]],"total_duration":536276168,"load_duration":396577084,"prompt_eval_count":2370}

Steps to Reproduce:

  1. Send a POST request to the /api/embed endpoint with a list input.
  2. Observe the HTTP response.

Expected Behavior:

The response should contain a single HTTP status "200 OK" without the intermediate "100 Continue" status.

Observed Behavior:

The response contains two HTTP statuses: "100 Continue" and "HTTP/1.1 200 OK".

Relevant log output

OS

Linux

GPU

Nvidia

CPU

No response

Ollama version

0.6.4

Originally created by @dev-quentin on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10126 ### What is the issue? When sending a list input to the `POST /api/embed` endpoint, we encounter an issue where the response contains two HTTP statuses: "100 Continue" and "HTTP/1.1 200 OK". Here is an example of the response received: ```plaintext HTTP/1.1 100 Continue HTTP/1.1 200 OK Content-Type: application/json; charset=utf-8 Date: Fri, 04 Apr 2025 12:25:29 GMT Transfer-Encoding: chunked {"model":"nomic-embed-text:latest","embeddings": [[...]],"total_duration":536276168,"load_duration":396577084,"prompt_eval_count":2370} ``` **Steps to Reproduce:** 1. Send a POST request to the `/api/embed` endpoint with a list input. 2. Observe the HTTP response. **Expected Behavior:** The response should contain a single HTTP status "200 OK" without the intermediate "100 Continue" status. **Observed Behavior:** The response contains two HTTP statuses: "100 Continue" and "HTTP/1.1 200 OK". ### Relevant log output ```shell ``` ### OS Linux ### GPU Nvidia ### CPU _No response_ ### Ollama version 0.6.4
GiteaMirror added the bug label 2026-04-22 13:37:22 -05:00
GiteaMirror commented 2026-04-22 13:37:24 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 7, 2025):

Could you provide more information on the environment and input? I was unable to reproduce.

$ curl -s -D /dev/tty localhost:11434/api/embed -d '{"model":"nomic-embed-text:latest","input":['"$(seq -f '"now is the time for all good men to come to the aid of the party line %f"' -s , 1 100)"']}' | jq '.embeddings=[.embeddings|length]'
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Date: Mon, 07 Apr 2025 14:17:04 GMT
Transfer-Encoding: chunked

{
  "model": "nomic-embed-text:latest",
  "embeddings": [
    100
  ],
  "total_duration": 742107054,
  "load_duration": 30776963,
  "prompt_eval_count": 2200
}
<!-- gh-comment-id:2783509398 --> @rick-github commented on GitHub (Apr 7, 2025): Could you provide more information on the environment and input? I was unable to reproduce. ```console $ curl -s -D /dev/tty localhost:11434/api/embed -d '{"model":"nomic-embed-text:latest","input":['"$(seq -f '"now is the time for all good men to come to the aid of the party line %f"' -s , 1 100)"']}' | jq '.embeddings=[.embeddings|length]' HTTP/1.1 200 OK Content-Type: application/json; charset=utf-8 Date: Mon, 07 Apr 2025 14:17:04 GMT Transfer-Encoding: chunked { "model": "nomic-embed-text:latest", "embeddings": [ 100 ], "total_duration": 742107054, "load_duration": 30776963, "prompt_eval_count": 2200 } ```
GiteaMirror commented 2026-04-22 13:37:25 -05:00
Author
Owner
Copy Link

@dev-quentin commented on GitHub (Apr 8, 2025):

Hello,

Thank you for your message. But I could not reproduce the problem.
I am closing this request. Sorry for the inconvenience.

<!-- gh-comment-id:2786321515 --> @dev-quentin commented on GitHub (Apr 8, 2025): Hello, Thank you for your message. But I could not reproduce the problem. I am closing this request. Sorry for the inconvenience.
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#32405
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?