Menu

#6 HTTP::Daemon closed socket problem

open
nobody
None
5
2001-02-10
2001-02-10
No

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.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.