mdedetrich commented on issue #59: URL: https://github.com/apache/incubator-pekko-http/issues/59#issuecomment-1630533493
> there's currently no way to signal non-fatal parsing errors (should we treat it non-fatal, though?) to the demuxer, so in any case the connection will be torn down after sending the response, together with all other ongoing streams. This seems to make it more reasonable to handle these HTTP-layer errors (as opposed to HTTP/2-framing errors) with HTTP error codes which however means that we need to find ways to signal those errors through the layers (i.e. introduce another synthetic frame type). So I don't know HTTP2 very in depth, but this to me appears like a non-fatal/business logic error (i.e. it happens when the client sends a malformed URI so its in the same class of errors like validation). If as you say there is no way currently for the HTTP2 to gracefully handle business/validation errors, we should probably fix that first before approaching this. @pjfanning Considering whats just been said I think its safer to park this for now and remove it from the 1.0.0 milestone -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
