Bug 35702 - Using with https URL, ab freezes or gets SIGSEGV on 2.1.6-alpha
Summary: Using with https URL, ab freezes or gets SIGSEGV on 2.1.6-alpha
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: support (show other bugs)
Version: 2.1-HEAD
Hardware: All All
: P3 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on: 35701
  Show dependency tree
Reported: 2005-07-12 13:41 UTC by Masaoki Kobayashi
Modified: 2018-11-07 21:10 UTC (History)
0 users

Path for ab in httpd 2.1.6-alpha (6.79 KB, patch)
2005-07-12 13:45 UTC, Masaoki Kobayashi
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Masaoki Kobayashi 2005-07-12 13:41:34 UTC
Because of historical apache library implementation, ab does apr_pollset_add()
multiple times for the same port.  It causes some confusion and inefficiency
inside pollset structure.
The behavior varies by the operating system because APR-1.x uses different
asynchronous I/O by operating systems.
i.e. port.c for Solaris 10, epoll.c for Linux 2.6, and kqueue.c for recent BSD.
When I use ab with "https:" URL, ab freezes on Solaris 10 while it gets SIGSEGV
on Linux.  There is another problem in apr/poll/unix/port.c as I reported on bug
#35701.  We have to fix both.
Comment 1 Masaoki Kobayashi 2005-07-12 13:45:25 UTC
Created attachment 15653 [details]
Path for ab in httpd 2.1.6-alpha

This patch fixes the ab in 2.1.6-alpha package, to make the SSL connection work
properly.  I have tested this patch on Solaris 10 amd64 machine.
Comment 2 William A. Rowe Jr. 2018-11-07 21:10:02 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.