server : do not parse when flushing http headers - #24281
Merged
Merged
Conversation
ngxson
approved these changes
Jun 7, 2026
|
Thank you @aldehir ! |
ggerganov
approved these changes
Jun 8, 2026
adrianhoehne
pushed a commit
to adrianhoehne/llama.cpp
that referenced
this pull request
Jul 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
When flushing http headers, the parse function is called and silently strips content we want to retain that is part of the generation prompt. This PR suppressing that initial parse so that content is kept. The most common usage is when
reasoning_format = noneand we want to retain the initial<think>tag that is part of the generation prompt. However, this can surface as well when continuing a message andecho = true.ref: #23320 (comment)