hugh williams writes:
> My question still remains - what changed in Apache that a construct it
> formerly parsed one way is now treated differently? Or not so much
> what changed, but why? Why does Apache now "care" what is inside an
> exec cmd' string?
Even in 1.3, mod_include interpreted $ in
Hi Dan;
Yes, that silences the errors, thanks!
My question still remains - what changed in Apache that a construct it
formerly parsed one way is now treated differently? Or not so much what
changed, but why? Why does Apache now "care" what is inside an 'exec
cmd' string?
Thanks again, now a
hugh williams writes:
>>
>>
>> This works fine in both Apache 1.3.33 and 2.2.3; however 2.2.3 also
>> send the following error warning into the error log:
>>
>> [Wed Oct 22 14:50:00 2008] [warn] [client xxx.xxx.xxx.xxx] regex
>> capture $1 refers to no regex in /users/hughw/public_html/spclhand/
Hi;
I posted this 5 months ago, and got no response. So I'm going to act
insanely (insanity: doing the same thing over and expecting different
results) and repost in hopes that some different readers are here.
Why is Apache 2.2.x throwing these warnings? I have upgraded to 2.2.9
since postin
