Project

General

Profile

Actions

Bug #2688

closed

[PATCH] LightyTest.pm: do not shutdown on darwin

Added by mackyle about 9 years ago. Updated over 8 years ago.

Status:
Fixed
Priority:
Normal
Category:
test_component
Target version:
ASK QUESTIONS IN Forums:

Description

While shutting down the sending side of a socket after having
sent the last of the data should not interfere with any future
reception of new data on the same socket, on darwin it does.

If the socket is shutdown for sending, it will fail to receive
any future data from the other end as well unless it already
just happens to be in the receive buffer waiting to be read.

Prevent this problem by skipping the socket shutdown on the
darwin platform which allows the tests to run to normal
completion and pass.

It's unclear whether or not this problem is limited only to
Perl or is system wide.

Patch file attached.

See also http://repo.or.cz/lighttpd/svnmirror/patches.git/commitdiff/97313367


Files


Related issues 1 (0 open1 closed)

Related to Bug #2743: 1.4.40/41 mod_proxy, mod_scgi may trigger POLLHUP on *BSD,DarwinFixed2016-08-02Actions
Actions #1

Updated by stbuehler about 9 years ago

  • Target version changed from 1.4.x to 1.4.38

Hm, I think we probably shouldn't send close on any platform (as that usually is taken as a "I don't need the response anymore" signal by the webserver) before we finished reading the response. I'll try to get this one in for 1.4.38.

Actions #2

Updated by stbuehler about 9 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset r3058.

Actions #3

Updated by gstrauss over 8 years ago

  • Related to Bug #2743: 1.4.40/41 mod_proxy, mod_scgi may trigger POLLHUP on *BSD,Darwin added
Actions #4

Updated by gstrauss over 8 years ago

It's unclear whether or not this problem is limited only to Perl or is system wide.

It appears to be a problem on Darwin and likely also *BSDs. See #2743

Actions

Also available in: Atom