Moved several CHANGES back to APR where they belonged in the first place,
  Adopt apr features for simplifing mod_userdir, and accept the new
  Win32/OS2 exceptions without hiccuping

  Also note a potentially serious flaw - others please review.


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

  Moving a small OS2'ism into APR, it's pw_dir excludes the username.
  Return the expected result.  Also noted the headers/os2errno changes
  from early this morning.


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

environment variable OPTIM instead.  This is needed because configure
options do not support multiple flags separated by spaces.


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

"-999999" where that is past the end of the file, we should return
a PARTIAL CONTENT status code, and return the whole file as one big
byterange.  This matches the 1.3 handling now.  [Ryan Bloom]


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

bucket length is 0, and a read returns NULL data.  If one of these
buckets is passed down after the headers are sent, this data will
just be ignored.
Submitted by:	Greg Stein


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

signal was received while the process was serving a request.  The child
process would become the equivalent of a second parent process.  If
we break out of the accept loop, then we need to do die after cleaning
up after ourselves.


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

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

  Use the appropriate APR_FINFO_flags for the apr_stat/lstat/getfileinfo
  calls to avoid ownership and permissions on Win32 when they are not
  required, and until they are implemented.


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

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

by sending a brigade where the first bucket is an error_bucket.
This bucket is a simple bucket that stores an HTTP error and
a string.  Currently the string is not used, but it may be needed
to output an error log.  The http_header_filter will find this
bucket, and output the error text, and then return
AP_FILTER_ERROR, which informs the server that the error web page
has already been sent.


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

bug where we were using the byterange filter to filter an error, which
caused us to close the connection before we had sent any data.  Currently,
we only keep the three most important filters, but we may need to add more
in the future.  I am mostly thinking of the charset translation filter.


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

are sensitive to the filesystem are rejected, i.e. forward slashes,
backward slashes, and sequences of more than one dot. This supports iDNS
without compromising the safety of mass vhosting.

PR: 6635


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

and apr_bucket_copy functions.  This removes a lot of very messy
code, and hopefully makes this filter more stable.


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

much sense anymore, since we use the hooks to order modules correctly.
This also removes the possability that one module will ever register the
same function for the same hook twice.


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

automatically.  This bit me multiple times last night as I was trying to
setup apache.org.  I would make a change to the configuration, run make;
make install, and it would fail.  The problem was that suexec wasn't
getting re-compiled ever, so my changes weren't getting picked up.  This
solves that problem, by making sure that suexec gets compiled if it was
specified on the configure line.


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

  Sunny in Chicago.


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

mpm_common.c.  These functions are only valid on some platforms,
so they should not be in the main-line code.

These functions are also not portable to non-unix platforms, so they don't
really belong in APR.  Since they are only used in MPMs, for right now,
I am moving them to mpm_common.c


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

is currently using it.  The proper way to do this, is to use the
apr_create_process API.


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

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

wrong commit incantation


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

for a fact that it isn't.  Basically, if r->connection->keepalive == 0.
This keeps us from making an extra read call when serving a 1.0
request.
Submitted by:	  Ryan Bloom and Greg Stein


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

I broke mod_rewrite by modifying strings in place when expanding them,
because variable lookups can cause subrequests which cause mod_rewrite
to do its stuff again including an expansion on the same string, which
is then syntactically invalid. So copy the lookup keys somewhere else
before using them in such a way that may cause recursion.

In addition to this, my parser could also be confused by complicated
nested rewrite map expansions like ${map1:${map2:key|dflt}|dflt} so
fix that too by keeping track of {} when looking for |.

PR:             7087


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

Host: header.

PR:             7079
Submitted by:   Alexey Toptygin <alexeyt@wam.umd.edu>


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

other folks were hitting a problem with mod_dav and need an excuse to
upgrade


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

and the server dropped the connection unexpectedly.


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

discarding the body of a request, but it could affect other paths.


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

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

hints.m4 works and the additional of NOTEST_*


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

we use the -D command line argument to Apache to configure these
options.
Submitted by:	Greg Stein


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

PR:
Obtained from:
Submitted by:
Reviewed by:


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

We copy the data when we store it in the structures, we can just return
a pointer from there, and use const data.  This puts the onus back on
Apache to copy the data if it needs to modify it.


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

(errno instead of apr_status).

mod_cgid: Keep some of the code in synch with the version in mod_cgi.


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

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

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

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

program does not exist.

I wish I understood why I didn't hit this problem in the normal
case :(


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

problem they fix


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

problem is that some browsers send an extra line at the end of a POST
request.  We use the PEEK method to determine if there is any data left
on the socket, if there is then we delay sending the response until we
have enough data to make it worthwhile.  If the browser sends an extra
blank line, we don't want to delay the response at all.  The only time
we use the PEEK method is to check for a second request, so this is safe
to do.

This also solves Joe Orton's problem of specifying a Content- Length
of 1 for a blank line, and having the server wait to send back a response.
The problem is that Linux (all Unix really) sends two characters \r\n for
a blank line, so specifying a C-L of 1 means that the server still sees
a \n when it PEEKs that the socket data.  That \n can be safely ignored
however.


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

changes made using autoconf setup.


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

allows the decisions made in one config.m4 file to be based on decisions
made in previous config.m4 files.  For example, the config.m4 in the
generators config.m4 can choose the correc cgi module based on which MPM
is chosen.

To do this, we find all filenames config*.m4, and then we re-order the
filename so that it looks like:  *config.m4/path/to/file.  Once all files
are in this format, we sort the files, and then re-arrange the file names
again to put them in the correct order.  There may be better ways to do
this, but I couldn't find a portable way to call sort so that this would
work.


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