Thanks a lot. Traced this issue at server side with respect to flow control. On fixing, we don't see this behaviour now.
On Thu, Nov 18, 2021 at 3:53 PM Daniel Stenberg <[email protected]> wrote: > > On Thu, 18 Nov 2021, Kunal Ekawde via curl-library wrote: > > > At the server, since DATA is not complete at 13:25:55, it cannot process > > until balance DATA is transmitted. > > > > Any pointer as to why / in which conditions, libcurl can delay sending the > > DATA packets ? > > I can't find a reasonable explanation for that. It needs to be > debugged/investigated I think. Add trace-points and debug output in the code > and monitor/compare what wireshark and the server side think of the > connection. > > Maybe related to issue #7977: https://github.com/curl/curl/issues/7977 ? > > > libcurl sending more amount of DATA frames crossing WINDOW_UPDATE specified > > by server ? > > I don't understand this question, Can you elaborate? > > -- > > / daniel.haxx.se > | Commercial curl support up to 24x7 is available! > | Private help, bug fixes, support, ports, new features > | https://curl.se/support.html -- ~Kunal -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
