How to handle Broken Pipe

• To: "'lib-friends@w3.org'" <lib-friends@w3.org>, "'www-lib@w3.org'" <www-lib@w3.org>
• Subject: How to handle Broken Pipe
• From: Vu Nguyen <vu@isdnsys.com>
• Date: Thu, 15 Feb 1996 18:11:24 -0500
• From vu@isdnsys.com Thu Feb 15 18: 06:15 1996
• Message-Id: <01BAFBD1.05DB3A60@vun.isdnsys.com>
• Return-Receipt-To: <vu@isdnsys.com>
• X-Info: ISDN Technology Leaders

While testing my server which is based on the Mini Server, I ran into this problem:  If I issue a request for a document from the browser and, then hit the 'Stop' button while the document being transferred then I have a broken pipe.  This occurs in HTWriter_write (HTStream * me, CONST char * buf, int len)

below is the line which adds the error into the request's error list

HTRequest_addSystemError(request,  ERR_FATAL, socerrno, NO, "NETWRITE");

which generates:

Error Add... number:  44        Severity: 1     Parameter: `NETWRITE: Broken pipe'      Where: `NETWRITE'

Why didn't SetSignal() do what it supposed to do?  and how would I handle it?

TIA,

Vu Nguyen

• Prev: PUT on Windows NT
• Next: Libwww Ver 4.0D - Dir Browsing problem
• Index: Message index of www-lib@w3.org mailing list
• Thread: Thread index of www-lib@w3.org mailing list