Repository navigation
Clarify incomplete proxy responses - #705
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Sayan-
marked this pull request as ready for review
October 19, 2026 16:23
hiroTamada
approved these changes
Oct 19, 2026
This branch was successfully deployed
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
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.
Clarify when
origin_response_incompleteis returned and what clients see when a connection drops after response headers. Retrying can still duplicate an operation that already succeeded.Publish after the proxy fix is deployed.
Validation: loaded
/proxies/errorsin the Mintlify preview and checked the updated text.Note
Low Risk
Documentation-only change to proxy error descriptions; no runtime or API behavior changes in this PR.
Overview
Updates the Proxy Errors docs to align
origin_response_incompletewith when Kernel can surface it: the failure is framed as the connection closing or stalling before response headers reach Kernel, not merely an incomplete body.Adds a short note that drops after headers are delivered show up as truncated responses or browser network errors, with no
502orX-Kernel-Proxy-Errorfrom Kernel. Existing guidance on safe retries and telemetry gaps for this code is unchanged.Reviewed by Cursor Bugbot for commit ac679e8. Bugbot is set up for automated code reviews on this repo. Configure here.