David Wheeler <[EMAIL PROTECTED]> writes: [...]
> Dammit, what are you doing to this thing, Ken? ;-) I've never had a > problem with the patch before, and the new version of it worked for me > on Jaguar. Very strange. > > Joe, any idea what could be causing the errors that Ken is getting? Nope :-(. It doesn't look like the apreq patch is causing the errors. It looks more like apache's APACI is hosed on his machine. I'd recommend retrying with a fresh apache tree, maybe even from 1.3's latest cvs. -- Joe Schaefer
