to read the release notes and apply patches to deal with this sort of thing.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93205 13f79535-47bb-0310-9956-ffa450edef68

  it be indicated in the 2.0.31 release notes?  Voice your opinions.
- The worker CGI test failure Ken sees seems to be a problem with
  perl or httpd-test as no one else seems to be able to reproduce it.
  So, let's try to demote this.
- I have no earthly idea what rbb is talking about.  Whatever it may be,
  I can't fathom that it'd stop a release.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93204 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93203 13f79535-47bb-0310-9956-ffa450edef68

I want to see a core.  0 bytes reads are fine.  Grr.

(I'm so tempted to throw this assert out, but if we get -1 length
brigades back, we're gonna be screwed.)


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93202 13f79535-47bb-0310-9956-ffa450edef68

other platforms.)


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93201 13f79535-47bb-0310-9956-ffa450edef68

Not okay with the two parents idea.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93200 13f79535-47bb-0310-9956-ffa450edef68

vote and decide...


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93199 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93197 13f79535-47bb-0310-9956-ffa450edef68

calls. Still lots of cleanup work to do here...


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93196 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93195 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93194 13f79535-47bb-0310-9956-ffa450edef68

need to cleanup where some bytes are stored, check-in routines this module
calls in cache_util, etc.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93193 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93192 13f79535-47bb-0310-9956-ffa450edef68

we should be more concerned with keeping the parent rock solid than adding
extra layers to protect the children from a broken parent.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93191 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93190 13f79535-47bb-0310-9956-ffa450edef68

I'm fine with adjusting that script in a -beta tarball since it isn't a
code change.  However, since official binbuilds are contributed by
committers only, this isn't a big deal as they can be smart enough to
use the updated script anyway.  And, binbuild has some other issues that
will be addressed shortly.  So, even if it doesn't happen, oh well.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93189 13f79535-47bb-0310-9956-ffa450edef68

and constify it while I'm at it.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93188 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93187 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93186 13f79535-47bb-0310-9956-ffa450edef68

Demote entries until there is majority support for showstopper status.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93185 13f79535-47bb-0310-9956-ffa450edef68

tree so that there aren't any surprises on the target machine.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93184 13f79535-47bb-0310-9956-ffa450edef68

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93183 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93182 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93181 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93175 13f79535-47bb-0310-9956-ffa450edef68

- ap_[r]getline rewrite has landed.  I think it is time for this STATUS
  item to be removed.  Is there anything more w.r.t. input filtering
  that needs to be addressed?


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93174 13f79535-47bb-0310-9956-ffa450edef68

Submitted by: Zack Weinberg <zack@codesourcery.com>


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93172 13f79535-47bb-0310-9956-ffa450edef68

modules to completely take over all network i/o from the core.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93171 13f79535-47bb-0310-9956-ffa450edef68

enough to keep up with new requests.  Start using
HTTP_SERVER_UNAVAILABLE instead of HTTP_INTERNAL_SERVER_ERROR
when we can't talk to the daemon.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93170 13f79535-47bb-0310-9956-ffa450edef68

Previously you had to edit the generated apxs to get rid of --silent.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93168 13f79535-47bb-0310-9956-ffa450edef68

to the global variable ap_scoreboard_shm.  Since this variable was already
being excluded by APR_HAS_SHARED_MEMORY at the beginning of the
file.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93166 13f79535-47bb-0310-9956-ffa450edef68

sorry for the spam
PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93165 13f79535-47bb-0310-9956-ffa450edef68

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93164 13f79535-47bb-0310-9956-ffa450edef68

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93163 13f79535-47bb-0310-9956-ffa450edef68

- Can we *ever* build a static binary?  That *is* a showstopper, I agree.
  And, Aaron has volunteered to fix this soon-ish.
- Separate from that, is the question whether we should we *always* build a
  static binary?  That I do not believe I *is* a showstopper.  So, let's
  make the distinction and call for a vote.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93162 13f79535-47bb-0310-9956-ffa450edef68

unregistered.  This fixes the 88 unreleased resources after termination


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93161 13f79535-47bb-0310-9956-ffa450edef68

survives graceful restarts. This fixes a SEGV during graceful restarts.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93160 13f79535-47bb-0310-9956-ffa450edef68

survives graceful restarts. This fixes a SEGV during graceful restarts.

Children who attach to this scoreboard keep the same pool as before (pchild)
since they should detach/unmap when the child process exits.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93159 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93158 13f79535-47bb-0310-9956-ffa450edef68

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@93157 13f79535-47bb-0310-9956-ffa450edef68