Open
Conversation
marcin-cebo
requested review from
jakub-grzesiowski,
jguz-pubnub,
kleewho and
parfeon
as code owners
jguz-pubnub
approved these changes
Feb 18, 2026
…ssages client gets socket close instead of 413 error. I tried with “Expect: 100-continue” header that works for oversize messages but for regular messages e.g. 100KB causes server not sending 100 continue status code resulting in client waiting till timeout and not sending request body to server.
marcin-cebo
force-pushed
the
2MB_message
branch
from
de6da0a to
f282673
Compare
Fixed logging interceptor no longer consume the response body, so server error now properly reach CoreEndpoint
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
2 participants
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.
No description provided.