One more backport for win32... aaa overhauld linkages aren't applicable.


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

"Per Greg's request, add a version string component to the ap_provider.h
 functions.  This allows modules to register different versions of the
 same provider."

Reviewed by:	Will Rowe


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

  Reflect the ap_provider [no mention of aaa rewrite here.]


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

  WHOA!  Fix the collatteral damage I caused by removing provider.

  mod_dav is also retrofitted for the generic ap_provider API.  Restore
  it to its 2.1 state for mod_dav (and of course, if someone wants to
  backport the aaa changes without the module names overhaul, they will
  need this API.)


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

  Reflect the real scope of changes in CHANGES for APACHE_2_0_BRANCH


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

  Somehow CVS missed this one.  Revert the aaa overhaul from the Win32
  build workspace.


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

  Thought this was done in the previous commit.  All aaa overhaul changes
  should be reverted now in APACHE_2_0_BRANCH, except for binary build files
  for the Netware platform.


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

  Revert the last bits of the aaa overhaul I could identify.


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

by Tim Gerundt <tim@gerundt.de>


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

  Back out provider.c from aaa 2.1 overhaul, for the time being.


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

  Unroll the 2.0 -> auth_rewrite changes from APACHE_2_0_BRANCH development


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

  Begin removing 2.1 auth rewrite from the APACHE_2_0_BRANCH for release
  sometime next week.  Given some odd segfaults with respect to some
  recombinations of new-aaa modules, I gathered that Justin now concurs
  with this overhaul as a 2.1 effort [2.2 release].


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

  announcements list.

  PR: 14892


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

by Tim Gerundt <tim@gerundt.de>
with some minor changes from me


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

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

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

'APACHE_2_0_BRANCH'.

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

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

nobody seems to have objections...

* XHTML 1._0_. delivering xhtml 1.1 as text/html is bogus.
  (see <http://www.w3.org/TR/xhtml-media-types/#summary>)
* replaced the also bogus <dl> stuff by normal <p>s
  and added some CSS instead.
  (embedding CSS compatible to xml *and* html causes the very
  ugly hack, you can see in top.html, because in HTML <style> contains
  CDATA and in XHTML PCDATA, see also
  <http://lists.w3.org/Archives/Public/www-html/2002Apr/0053.html>)
* fixed some encoding issues.
* removed the weird empty lines at the beginning of every document
* added CONTENT_LANGUAGE parameter for pt-br


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

Since nobody knows how to update the man pages this functionality has gone
undocumented.


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

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

PR:
Obtained from:
Submitted by:
Reviewed by:


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

  Patches now committed


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

  Set the appropriate mime response headers for negotated type-map
  Body: responses.

  wrowe's review;
    My earlier concern doesn't apply.  Type maps have always required the
    author to be explicit in all header fields to be negotiated; if the
    headers aren't given in the type map file the resulting redirect
    (for non-body maps) is broken anyways.  As to my other concern, the
    charset should only exist if the Content-Type was given.

Backport rev: 1.109
Submitted by: Andr� Malo <nd@perlig.de>


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

  Accept '%%' in CustomLog format strings to produce a literal '%'.

Submitted by: Andr� Malo <nd@perlig.de>


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

back to r-t-c, and that 1.3 is used by a *lot* more people
and so stability must be even more of a concern, I fail
to see why we need to move to a r-t-c for the 2.0 branch to
"ensure" stability or for any of the other suggested reasons.

Certainly any issues with the 1.3 release problems will themselves
be moot since the release procedure for 2.x is very different.
r-t-c, IMO, will do little more than stifle development on
a tree that really requires *more* development.

PR:
Obtained from:
Submitted by:
Reviewed by:


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

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

  Same patch from 2.1-dev ... quiet the noise


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

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

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

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

  Reflect the CTR/RTC is a simple vote, not a change/nochange technical
  sort of decision.

  Pull an unnecessary vote.  The real vote will be about 2.2.  But we are
  all about not breaking 2.0 users, and that means leaving experimental for
  those already experimenting :-)


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

  Revert assertions based on JimJ's, Aaron's and Cliff's feedback.


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

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

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

  Out here it's time for some cleanup of auth.


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

  The roadmap means nothing in the 2_0 branch ... let's maintain it on the
  sandbox branch alone.  Fix some notes in STATUS and remove or warn against
  some changes for the lifetime of 2.0.


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

'APACHE_2_0_BRANCH'.

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

  Catch up with Trawick's change to filters/mod_ext_filter


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

now work as in Apache 1.3, where no trailing '/' is
specified on the directory name.  Previously, the trailing
'/' *had* to be specified, which was incompatible with
Apache 1.3.

PR:       7990


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