ok2c commented on PR #709: URL: https://github.com/apache/httpcomponents-client/pull/709#issuecomment-3221451400
> > The HTTP/1.1 protocol handler by default aggressively pipelines request messages. > > That's an important detail. How does this work? Does pipelining only kick in when the max connection pool size is reached? How does this interact with the `connectionRequestTimeout`? How can pipelining be disabled? Which version of the client enabled pipelining by default? @rschmitt HTTP/1.1 protocol handler has been working like that since 5.0-alpha1. Requests have always been immediately written out to the connection as soon as submitted by the caller for execution. I do not see a reason why it should be different. It is fully protocol conformant while dropping connection without signalling it is not. If you insist we can add a config knob to disable it. -- 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]
