Good work Mr. RM :)


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

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

docs.  Details will be at
http://httpd.apache.org/docs-project/docsformat.html
shortly.


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

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

more idiot proof.

Also, move UseCanonicalName to directly under ServerName to make the
connection clearer, and clean up the comments.

I removed the http://123.123.123.231/ example, because it just makes it
too tempting for people to use
ServerName http://123.23.23.23/


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

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

It's getting closer to working but still a ways off.


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

  These files cannot be distributed at present - Justin, update your RC.32

  Win32 is not escaping or rejecting ANY hazerdous shell command strings
  in Apache 2.0 at present.  These would include the pipe character (|)
  which allows the user to construct malicious request strings.

  This needs consideration in code and configuration before we reintroduce
  a batch-file based example.

  Reported by: Ory Segal <ORY.SEGAL@SANCTUMINC.COM>  13 Feb 2002


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

*Please* test.


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

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

disk_cache_object_t.


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

some problems with the new POD code in the worker MPM, and although
I'm almost finished I didn't want people rolling a tarball without
knowing of these problems first.


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

per-transaction pools instead of destroying them.  Based on
Ian's benchmark testing, this reduces CPU utilization by
about 1% on Solaris.


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

  The final commit to achieve a quality release.  We cannot use CreateThread
  on Win32 when using the clib; msvcrt has its own initialization and
  destruction, so it needs its own turn.  _createthreadex is the same but
  different - it's implemented by msvcrt and causes all the appropriate
  setup and teardown to occur.


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

  Spell out some changes


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

  Address the issue raised on list that users with a LanguagePriority
  directive alone expect 'ForceLanguagePriority Prefer' behavior even
  if that directive is omitted.


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

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

  What happened?  0.9.6b built just dandy without the flags... 0.9.6c won't
  build for jack without these changes.  Of course they don't harm 0.9.6b
  builders either, unless they are outside of the states/EU/AU and find
  themselves free to ignore IP considerations.

  I'd really like to know _why_ 0.9.6c doesn't configure itself rationally.


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

also.. changed the logic slightly.
it will remove the name retrieved, not what the object has.

sorry for the spam.


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

obj was set before the mutex so someone could have came and updated h->cache_obj
between us setting obj, and useing it.
running now for 10 minutes without core (a record!)


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

2 threads both trying to remove the same URL at the same time.


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

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

By the way, it seems many people are considering moving to 2.0 just to get
"integrated ldap support".  I guess they will be disappointed.


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

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

  After hours of debugging, the answer was -trivial-, but extremely
  obscure and difficult to trace.  This should do away with the handle
  corruption we experienced.  If anyone cares to walk the crt (source
  is installed in vc\src\crt if you install it w/ Visual C++/Studio)
  it's worth understanding why this occured.

  This patch

    1. creates the pipe non-inherited, and dups the write end
       for inheritence with limited permissions.
    2. sets the STD_ERROR_HANDLE _after_ we fixup the FILE *stderr and fd 2.
    3. Splits the signal_monitor event in two, service_init/service_term
       for clarity and correctness.


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

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

PR: 9787


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

  Perform a serious scrubbing of the child process, before we report that
  we failed to create the child.  Cleans up CloseHandle() destruction to
  match all created handles - and postpone populating the *child_exit_event
  until we succeed.


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

  This code seriously misassumed (and may yet) that stderr was a valid file.
  It also has some bogus non-apr code that probably does great evil to win32
  services.  This must be bumped into .32, code review is incomplete still.


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

  Move the sleep until after we have duplicated the simple handles.  We must
  still pause and reflect on the Child's startup before WSADuplicateHandle()


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

to 1 per second until the situation clears up.

Inspired by: Martin Kraemer


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

  Never close the handle, if it is the StdError psuedohandle.


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

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

passed to a CloseHandle call.


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

for backward compatability.


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

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

we use the pipe of death for all communication between parent and child.


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

I don't have a strong opinion on what we should do if the parent dies, now
that we don't have a real life example of that any more.  It was a little
confusing at first, but OTOH it kept serving requests.


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

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

Primarily additional explanation and examples.


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