On 2024-07-06 at 05:59:57, Junio C Hamano wrote: > "brian m. carlson" <sandals@xxxxxxxxxxxxxxxxxxxx> writes: > > >> Buffering the entire thing will break because ...? Deadlock? Or is > >> there anything more subtle going on? > > > > When we use the smart HTTP protocol, the server sends keep-alive and > > status messages as one of the data streams, which is important because > > (a) the user is usually impatient and wants to know what's going on and > > (b) it may take a long time to pack the data, especially for large > > repositories, and sending no data may result in the connection being > > dropped or the client being served a 500 by an intermediate layer. We > > know this does happen and I've seen reports of it. > > And this is an example of "a proxy that buffers the data, without > modifying or tampering with, would still break transport"? Yes. The connection usually ends up dropped from the view of the client, which is hard to debug (because it also looks like a network problem, except often without any output from the remote side). -- brian m. carlson (they/them or he/him) Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
