Re: [patch] Update to libfetch

From: Dag-Erling Smørgrav (des_at_des.no)
Date: 02/22/05

  • Next message: Dag-Erling Smørgrav: "Re: [patch] Update to libfetch"
    To: Kelly Yancey <kbyanc@posi.net>
    Date: Tue, 22 Feb 2005 11:02:57 +0100
    
    

    Kelly Yancey <kbyanc@posi.net> writes:
    > Attached is a patch to address concerns raised by Pawel Worach with
    > regards to the recent change to set TCP_NOPUSH when sending HTTP
    > requests from libfetch. The previous revision also introduced a call
    > to shutdown(2) to close the write half of the socket in order to force
    > the queued request to be sent. While this should be perfectly
    > acceptable behavior for a TCP client, it appears that squid provides a
    > configuration option to disallow half-closed clients (which Pawel is
    > currently using). As such, after introducing the shutdown(2) call,
    > fetch(1) can no longer fetch files via HTTP through such proxies.
    > To address this issue, the attached patch replaces the call to
    > shutdown(2) with some socket option fiddling (clearing TCP_NOPUSH and
    > setting TCP_NODELAY) which does the same job of forcing the client to
    > write the queued request to the network without closing the write half
    > of the socket. This feels a bit hackish to me, but gets the job done.
    > Anyway, I would appreciate any feedback. Thanks,

    Doesn't simply reading from the socket or selecting it for reading
    flush the output queue?

    DES

    -- 
    Dag-Erling Smørgrav - des@des.no
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
    

  • Next message: Dag-Erling Smørgrav: "Re: [patch] Update to libfetch"

    Relevant Pages

    • RE: Underlying connection was closed
      ... When you say, this patch applied to 1.1, do you mean we ... configuration be incorrect as this happens ... Web Services Client: ... >The underlying connection was closed. ...
      (microsoft.public.dotnet.framework.webservices)
    • Re: Grr...
      ... entered my password and "We could not authenticate your login..." ... Looked up the number for Customer Support (after going through SEVERAL ... the client hadn't been updated. ... checking uo.stratics there HAD been a client patch last week. ...
      (rec.games.computer.ultima.online)
    • Re: Grr...
      ... Looked up the number for Customer Support (after going through SEVERAL ... trees of menus) and finally got a nice young Indian gentleman who ... the client hadn't been updated. ... checking uo.stratics there HAD been a client patch last week. ...
      (rec.games.computer.ultima.online)
    • Re: [patch] update: _working_ code to add device+inode check to ipt_owner.c
      ... so if nothing else, like the other ipt_owner things, this patch ... uid and gid associated with its socket. ... in fact, for servers which fork, this would be a problem. ...
      (Linux-Kernel)
    • Re: web updates that work with binary patches?
      ... Which support running the binary patch on the client to ... >with regular files (not binary patches). ...
      (borland.public.delphi.thirdpartytools.general)