Add x-amz-content-sha256 header to AskAi stream requests #2137
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
When using CloudFront with Origin Access Control (OAC) to secure Lambda Function URLs, POST requests require the x-amz-content-sha256 header for body integrity validation.
Solution
Added SHA256 hash computation in useFetchEventSource.ts for request body
Included x-amz-content-sha256 header in all POST requests to /ask-ai/stream
Used ES5-compatible hex formatting (avoiding padStart for broader browser support)
Why
Required by AWS CloudFront OAC to prove request body integrity from client to CloudFront. CloudFront handles the SigV4 signing; client only needs to compute the hash.
Impact: Enables secure streaming through CloudFront with OAC enabled, supporting the hybrid architecture for Lambda Function URLs.