[18.0][FIX] ai_oca_bridge: avoid crash when request charset is missing#64
Open
[18.0][FIX] ai_oca_bridge: avoid crash when request charset is missing#64
Conversation
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.
Problem
The async callback endpoint
/ai/response/<execution_id>/<token>decodes the raw request body withrequest.httprequest.charset.In some environments, the wrapped request object does not expose a
charsetattribute, which causes the callback to crash with:As a result, valid async callback payloads return HTTP 500 before
_process_response()is reached.Reproduction
A direct callback request also fails with HTTP 500:
Fix
Use a safe fallback to UTF-8 when the request object does not provide a charset:
Result
Async callback payloads such as:
{"body":"Record updated successfully"}can be processed without crashing when
request.httprequest.charsetis missing.Additional context
Possibly fixes issue #54