As I understand the HTTP protocol (that is, some but not lots), the most
reasonable thing for the server to do if it discovers an error after the
status code has been sent seems to be to just hang up and let the client
realize that *something* went wrong. I don't mean just truncate the output;
I
Thank you, Brian and Jesse, for your thoughts on this. There may still
be an exception problem here, though.
(and sorry for being sluggish to respond)
On 16 May 2020, at 20:16, Norman Gray wrote:
Now, in tracking this down I can see that I have a wrong design here:
the servlet has
Hi Norman,
On Saturday, May 16, 2020 at 9:16:18 PM UTC+2, Norman Gray wrote:
>
>
> But (a) what should I be doing? And (b) since that exception is caught
> in this with-handlers clause, what is it that's producing the (default)
> exception output message? And (c) should I expect the client
On Saturday, May 16, 2020 at 3:16:18 PM UTC-4, Norman Gray wrote:
>
> [...]
> The exception is thrown inside the 'output' procedure
> that's provided as the last argument to the 'response' constructor (I
> belatedly realise this is probably a bad idea).
> [...]
> But (a) what should I be doing?
4 matches
Mail list logo
