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
{{ message }}
Repository navigation
[v2] Regression: Response sended before first stream payload #1510
h3 v1 waited with sending the response until the first async stream payload. This allowed setting response status codes and headers from within a stream (as long as it was part of the first payload). In h3 v2 you must set response status codes and headers before returning the stream. Response changes made while async rendering the first stream payload are now ignored. This makes it impossible to set response status/headers depending on async data within stream based frameworks such as SolidStart.
changed the title [-]Regression: Response sended before first stream payload[/-][+][v2] Regression: Response sended before first stream payload[/+]on Jul 24, 2026
@katywings please check #1512 it can be fixed partially using iterable in next releease but not sure if we could really fix limit of web apis. please ping me to reopen if still want to discuss it.
@pi0#1512 indeed fixed the issue, thank you a lot ❤️🎉.
Different issue (I gonna open it tomorrow 🙏), but rc.26 unfortunately resulted in a different regression with merged cookie headers from event.response being set twice for some reason 🙈.
Edit: The cookie regression is probably unrelated to h3 🙂
Activity
[-]Regression: Response sended before first stream payload[/-][+][v2] Regression: Response sended before first stream payload[/+]fix: defer handler response until stream shell payload
fix: defer handler response until stream shell payload
pi0 commentedon Jul 24, 2026
I will check it might be a fundumental difference when we migrated to web apis.
btw any reason you are not using h3
iterableutil? to send reponsekatywings commentedon Jul 24, 2026
Thank you 🙂. No special reason, I didn't know
iterableexisted 😅fix(response): allow status and headers staged during the first strea…
pi0 commentedon Jul 24, 2026
@katywings please check #1512 it can be fixed partially using
iterablein next releease but not sure if we could really fix limit of web apis. please ping me to reopen if still want to discuss it.katywings commentedon Jul 24, 2026
@pi0 #1512 indeed fixed the issue, thank you a lot ❤️🎉.
Different issue (I gonna open it tomorrow 🙏), but rc.26 unfortunately resulted in a different regression with merged cookie headers from event.response being set twice for some reason 🙈.Edit: The cookie regression is probably unrelated to h3 🙂
fix: defer handler response until stream shell payload
fix: defer handler response until stream shell payload
fix: defer handler response until stream shell payload
fix: defer handler response until stream shell payload
fix: defer handler response until stream shell payload