Repository navigation
fix: match the event stream MIME type exactly - #369
Merged
Merged
Conversation
rexxars
force-pushed
the
rexxars/fix-event-stream-content-type
branch
from
October 13, 2026 20:45
321ce2a to
7bb1b1a
Compare
rexxars
marked this pull request as ready for review
October 13, 2026 20:50
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.
The current prefix check rejects
Text/Event-Streambut acceptstext/event-streaming. Match the completetext/event-streamtype case-insensitively, allowing HTTP whitespace around it and parameters after;.This is a smaller alternative to #366. It fixes the MIME matching with an inline regex and leaves parsing of combined or repeated
Content-Typeheaders out of scope to keep the bundle small.