Jesse Guardiani writes: >> Again, this all started when I upgraded my Apache version from 1.3.27 to >> 1.3.28 and upgraded the supporting modules and such.
I can fully confirm that this problem doesn't show up with apache 1.3.27, just with 1.3.28. Reverting back to the previous version solved the issue. Thanks to everyone for the advice! -- Mario
