You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, with HTTP1 shotgun is able to handle async SSE streams by using special logic when it detects the chunked transfer encoding header. For HTTP2, which gun will use when available, shotgun will try to process it as a non-chunked request (since HTTP2 doesn't support chunking) and end up in gen_statem timeout.
It seems like we'll need a new HTTP2 way to handle streams.
The text was updated successfully, but these errors were encountered:
Currently, with HTTP1
shotgun
is able to handle async SSE streams by using special logic when it detects the chunked transfer encoding header. For HTTP2, whichgun
will use when available,shotgun
will try to process it as a non-chunked request (since HTTP2 doesn't support chunking) and end up ingen_statem
timeout.It seems like we'll need a new HTTP2 way to handle streams.
The text was updated successfully, but these errors were encountered: