Add "X-MKit-Chat-UUID" header support for streaming responses #22
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.
Updated CORS configuration to expose the "X-MKit-Chat-UUID" header. Enhanced the streaming setup to include the chat UUID in response headers when available, improving traceability and debugging for client applications.
This pull request includes changes to add support for exposing and handling a new header,
X-MKit-Chat-UUID
, in the API. The most important changes include modifying the CORS configuration, updating the streaming headers setup, and ensuring the new header is included when available.Changes to CORS configuration:
cmd/api.go
: AddedX-MKit-Chat-UUID
to the list of exposed headers in the CORS configuration.Updates to streaming headers setup:
internal/handler/chat.go
: Updated thesetupStreamingHeaders
function to accept an additionalchatUUID
parameter and set theX-MKit-Chat-UUID
header if the UUID is available.internal/handler/chat.go
: Modified theHandleAskStream
function to extract the chat UUID from the request context and pass it to thesetupStreamingHeaders
function.