I mucked up my content length header, leaving it too short.
curl disconnected after receiving the prescribed amount of content. (Or wasi-http disconnected after serving the prescribed amount of content. Something.)
Spin got mad and told me I had a "Component error after response started."
The amount of time I spent trying to track that error down in my code.
Anyway I dunno if this is feasible but I would love it if we could provide an error saying "the client disconnected while we were still sending data." I mean, yes, there was a component error, but the message implies something like "it panicked while streaming" rather than "you mucked up your content-length you bearded twit."
I mucked up my content length header, leaving it too short.
curl disconnected after receiving the prescribed amount of content. (Or wasi-http disconnected after serving the prescribed amount of content. Something.)
Spin got mad and told me I had a "Component error after response started."
The amount of time I spent trying to track that error down in my code.
Anyway I dunno if this is feasible but I would love it if we could provide an error saying "the client disconnected while we were still sending data." I mean, yes, there was a component error, but the message implies something like "it panicked while streaming" rather than "you mucked up your content-length you bearded twit."