[Bug #131826] HTTP::Daemon closed socket problem

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: James Munroe: "LWP::Parallel::UserAgent and MacPerl"
• Previous message: Coos Poland: "proxy , https and libwww"

Bug #131826, was updated on 2001-Feb-10 02:37
Here is a current snapshot of the bug.

Project: libwww-perl
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: drrho
Assigned to : nobody
Summary: HTTP::Daemon closed socket problem

Details: Maybe it is not a bug, but something which should be
addressed, IMHO.

When an HTTP client sends a request and closes the
connection before the daemon can react, it will eventually
write to a closed socket.

According to some UNICes this will cause a SIGPIPE
signal. If the process has no handler for this, it
will exit.

My best guess is to hide this inside the package
or allow the application to configure the appropriate
behavior such as an escalation.

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=131826&group_id=14630

• Next message: James Munroe: "LWP::Parallel::UserAgent and MacPerl"
• Previous message: Coos Poland: "proxy , https and libwww"