On Wed, Sep 12, 2018 at 12:48 PM Hemant Chaudhary <hemantdude.chaudhary@xxxxxxxxx> wrote: > > Actually it is setting sock->timeout to 0 in writev_nonblocking() in core_filters.c. > arv = apr_socket_timeout_set(s, 0); > > Why does the default timeout is changed and set to 0 ?? Because writev_nonblocking() is really non-blocking and should return EAGAIN/EWOULDBLOCK when things start to block. But writev_nonblocking() is a local function, called (indirectly) by the core output filter which deals with EAGAIN appropriately. Why is it an issue for mod_proxy_http? EAGAIN remains local to the core filtering, but however mod_proxy_http always passes a FLUSH bucket at the end of the body, so everything should be fine at the core filter level... Regards, Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|