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

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

and clarifications

Deemphasize and re-document min and smax, which are only to be
used in special circumstances.

Stop using the terms "Hard maximum" and "Soft maximum" since they
imply incorrectly that max and smax are closely related parameters
which should be considered in tandem.  That may be true from the
apr_reslist perspective, but not from that of the httpd admin.

Thanks, Rüdiger (but of course all bugs are mine)


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

process.


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

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

interface into the private cache_util.h interface.


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

out of mod_cache.h.


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

public prefixes from ap_cache_accept_headers, ap_cache_try_lock and
ap_cache_get_providers.


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

ap_cache_check_freshness private.


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

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

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

structure through mod_cache's function parameters in the usual way.


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

- remove old votes:
  * "what to do if parent dies" went nowhere after many years
  * we now have event MPM as default


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

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

about the connection pool and related parameters
(yes, and fix part of those earlier "clarifications")


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

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

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

directive to allow the user to override this questionable change.

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

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

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

from the origin server

apr_date_checkmask() already verified the expected text and digit
positions; all that is needed is to cheaply find which digits


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

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

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

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

or not cache based on the buckets present in the brigade, such as the
presence of a FILE bucket.


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

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

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

regexp operations.


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

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

serves to slow down the match process.


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

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

>= and <= syntax, added by wrowe in r997553.


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

  Let it take effect if we decide to store the body in a
  temporary file on disk.


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

Updating others to remotely match current pratice (i.e.: current Ciphers used, 1024 -> 2048 bits, etc)



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

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

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

be issued (since !n occurs when status != APR_SUCCESS)


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

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

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

translation. It would be nice if you could run './build.sh validate-xml'
before commiting.


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