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

fit the requirements of mod_proxy again.


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

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

when using shared objects. Because these lines have to be in front of any
directives which are contained in the module itself it is recommended to load
those modules at the top of httpd.conf.


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

- avoid gcc complains by define main as at the other places in the two new
  generation programs
- make uri_delim as all-in-one as test_char (#include in the middle of a
  struct definition is a little bit ugly)
- make the generated files readable even not editable
- remove double-defined dependencies in Makefile.tmpl (because they are
  already part of the "make depend" generated list)

PS: There seems to be another problem here: The files are
    generated in main/ and included with #include "...".
    Although we only have -I../include and -I../os/unix but
    not -I. ! Is it really portable for all compilers to
    assume the CWD is searched for #include "..." even
    if no -I. is used? I personally would change it so
    that the files are generated in ../include/. Comments?


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

us as well because they can avert "bug" reports.  Fix a few more... there's
dozens more that could do with improvements.


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

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

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

Submitted by:	jim <jim@nlenx.com>


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

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

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

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

We need to mark various bitfields as signed to follow the spec.


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

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

naming each beta release to come later, but, in short,
I think it just will cause major confusion for the outside world


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

fixes I've been thinking about are somewhere deep in my mind I can't
find at the moment.  I'm ready to "throw in the towel" so that unix
1.3.0 can get out there, and get into reviewer's hot little hands.  I
know of a few groups that want to benchmark it, but really would prefer
to benchmark something released.  I really don't want to see us with
win32 tied to unix release schedule forever... it's pointless.

It's all just names anyhow.  Whether we call it a beta or a current
release it's just a name.  It's time we at least had a "release candidate"
to use the 1.2 terminology... I'm with Roy, I want to drop the x.ybz
designations.  I want x.y.z, a single numbering scheme.


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

for graceful restarts.  Given that the only usage of SIGURG is now
protected by a #ifdef we don't really need the definition.  ... similarly
for BeOS, why define SIGBUS SIGSEGV?


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

properly marked for closure on fork().

PR:		2000
Submitted by:	J�rgen Keil <jk@tools.de>


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

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

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

Change to +0 my vote for inclusion APACI. I am still slightly tempted to -1,
but for no good reason other than the incredibly condescending comments
associated with it. This addition has been a classic exercise in social
and political ineptness. C'est la vie; it's good code. No release soon,
anyway, so I guess code freeze is over.


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

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

since these flags must be present both for compile and link


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

or in a proxy request (this shouldn't return a 404 anyway, but a 400)


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

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

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

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

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

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

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

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

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

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

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

be marked const and save on per-child memory requirements.

WIN32 folks, Ben said you could handle this... you've got to compile
something and then run it to generate the tables.


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

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

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

Obtained from:
Submitted by:
Reviewed by:
Add a new section where we just add Notes and Words Of Wisdom about
porting Apache to various platforms... Seemed to make better sense to
put it here rather than README (??)


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

Obtained from: Lars <lars@informatik.uni-siegen.de>
Submitted by:	Jim Jagielski
Reviewed by:
Add the SCO_SV port


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

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