fix(middleware): handle invalid request-id header values gracefully#61
Closed
echobt wants to merge 2 commits intodocs/standardize-timeout-documentationfrom
Closed
fix(middleware): handle invalid request-id header values gracefully#61echobt wants to merge 2 commits intodocs/standardize-timeout-documentationfrom
echobt wants to merge 2 commits intodocs/standardize-timeout-documentationfrom
Conversation
echobt
added a commit
that referenced
this pull request
Feb 4, 2026
This PR consolidates the following error handling fixes: - #48: Handle semaphore and init failures gracefully in async_utils - #54: Improve error handling in session storage operations (includes TOCTOU race fixes) - #55: Add validation for threshold, ratio, and token count fields - #56: Replace unwrap with proper error handling for client access - #57: Use unwrap_or_default for SystemTime operations - #61: Handle invalid request-id header values gracefully - #65: Improve error handling for timestamp and JSON operations in streaming Key changes: - Added graceful handling for semaphore and init failures - Bound ToolResponseStore size and cleanup consumed entries - Eliminated TOCTOU races in MCP server and plugin registry - Replaced unwrap() with proper error handling throughout - Added validation for config fields - Improved error propagation in middleware
Contributor
Author
|
Consolidated into #73 - fix: consolidated error handling improvements |
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
1 participant
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.
Summary
This PR addresses an unsafe
.unwrap()call in the request ID middleware that could cause a panic if the request ID contains invalid HTTP header characters.Problem
In
src/cortex-app-server/src/middleware.rs, therequest_id_middlewarefunction used.unwrap()when converting the request ID string to aHeaderValue:If a client provided a request ID header containing invalid characters (control characters, non-ASCII bytes, etc.), this would cause a panic and crash the request handler.
Solution
Replace the unsafe
.unwrap()with.unwrap_or_else()that provides a fallback value:This ensures that even when clients provide malformed request IDs, the server continues to function and returns a response with a safe fallback header value.
Testing
cargo check -p cortex-app-server