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
I'm not sure I fully understand this yet, but if I do, then by the time react-dom-stream gets to a component that throws an error, a status code of 200 has already been written to the response header and it's impossible to send a 500 if an error occurs.
Is this an intractable problem? Maybe you know how other streaming servers deal with this, I don't.
The text was updated successfully, but these errors were encountered:
@dmitry so I was confused by that article into thinking that X-Streaming-Error was a sort of standard, but obviously it's not because I can't find it anywhere else on the web. Chrome certainly didn't show any error message when I sent it in a trailer. If only status code were a header, then it would be so easy...
I'm not sure I fully understand this yet, but if I do, then by the time react-dom-stream gets to a component that throws an error, a status code of 200 has already been written to the response header and it's impossible to send a 500 if an error occurs.
Is this an intractable problem? Maybe you know how other streaming servers deal with this, I don't.
The text was updated successfully, but these errors were encountered: