I actually meant trying to catch a SIGPIPE when the client prematurely hits the Stop button in the browser, not when the socket is closed normally. If the server tries to write to a client that has disconnected from the socket, a SIGPIPE should occur, and it can be caught by the web server. Of course, you only get a SIGPIPE once you try to write to the socket, so if you're in the midst of some lengthy operation (where you don't write back to the client), you won't catch it right away.

I believe this is how one previously determined that clients pressed the Stop button under mod_perl, although after Apache 1.3.6, there's now a better way of doing it (checking the return value of $r->print).

In reply to RE: RE: Re: Questions on socket by btrott
in thread Questions on socket by Delfer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.