this value was ignored in favour of the current time. This meant
that Date headers on proxied requests where rewritten when they
should not have been.
PR:		14376
Obtained from:
Submitted by:
Reviewed by:


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

PR:
Obtained from:
Submitted by:
Reviewed by:


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

PR:
Obtained from:
Submitted by:
Reviewed by:


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

PR:
Obtained from:
Submitted by:
Reviewed by:


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

PR:		19023
Obtained from:
Submitted by:	Sami Tikka <sami.tikka@f-secure.com>
Reviewed by:


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

Note: the removed sequences ('esc $ B' 'esc ( B' (or other way round)) are ok.
These are useless "shift on"/"shift off" switches. See RFC 1468.


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

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

they are not transformed correctly.
This change defines the output to be exactly " " (without quotes)


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

httpd.spec.in, using build/get-version.sh from APR.
PR:
Obtained from:
Submitted by:
Reviewed by:


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

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

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

the relativepath element becomes obsolete.


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

Reviewed by: Astrid Ke�ler


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

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

The change is mainly intended to save some memory during the build process.
Additionally we may get a bit more clearness in our document structure ...


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

  Time for disclosure details

  If anyone sees credit-where-credit-is-due that I've missed, please
  add those individuals.


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

document but all variants of it (i.e. one basename), such as avail. languages,
formats etc.

(Note, that it's still a noop for the output.)


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

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

(not backported yet; but later)


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

least for url stability reasons.


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

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

name.  (Heck, I'm lucky if I get people to call me by my first name.)

Also split out something I didn't explicitly say as well, but may be true.


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

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

Submitted by:	Hiroaki KAWAI <hawk@bcl.t.u-tokyo.ac.jp>
Reviewed by:	Yoshiki Hayashi


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

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

future if we sind up with lots of versions.


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

backward-compatibility policy.  We assume that people preserve their
own config files, rather than going back to the default each time.


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

  Please consider and vote - see what this choice has done to us
  r.e. .tar.gz.md5 files and so forth.


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

a note on perchild:
  perchild exception handling was busted before this and is still busted
  the problem I noticed was that a client that exposes a segfault never
  gets its connection dropped and the parent never notices that the
  child process that segfaulted hasexited


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

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

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

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

We may have to experimt a bit to get best results. This is a first
attempt.


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

	Note this change (as previously written, it implied that 1.3.5
	had this vulnerability, which is not true). I'm not sure if
	"httpd 2.0" is the preferred name.

-    <p>Note that in versions previous to 2.0.46 no escaping has been performed
+    <p>Note that in httpd 2.0 versions prior to 2.0.46, no escaping was performed
     on the strings from <code>%...r</code>, <code>%...i</code> and
     <code>%...o</code>. This was mainly to comply with the requirements of
     the Common Log Format. This implied that clients could insert control
     characters into the log, so you had to be quite careful when dealing
     with raw log files.</p>

-    <p>For security reasons starting with 2.0.46 non-printable and
+    <p>For security reasons, starting with 2.0.46, non-printable and
     other special characters are escaped mostly by using
     <code>\x<var>hh</var></code> sequences, where <var>hh</var> stands for
     the hexadecimal representation of the raw byte. Exceptions from this
     rule are <code>"</code> and <code>\</code> which are escaped by prepending
-    a backslash, and all whitespace characters that are written in their
-    C-notation (<code>\n</code>, <code>\t</code> etc).</p>
+    a backslash, and all whitespace characters which are written in their
+    C-style notation (<code>\n</code>, <code>\t</code> etc).</p>


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

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

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

Submitted by:	Hiroaki KAWAI <hawk@bcl.t.u-tokyo.ac.jp>


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

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

Submitted by:	Hiroaki KAWAI <hawk@bcl.t.u-tokyo.ac.jp>


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

I changed the references to the auth modules, so that they're matching
the new model, but it probably needs a rewrite anyway.


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