Re: Errors in the wrong place and wrong format

file (the one specified for my virtual host) and warn errors in /var/log/apache2/error.log What on Earth could be the reason for that? Worik > > On Mon, Nov 17, 2014 at 6:28 PM, worik wrote: > >> > My virtual host has errors redirected to: >> > >> > Wori

Apache2::Connection::remote_ip

Can't locate object method "remote_ip" via package "Apache2::Connection Turns out I should have used $r->useragent_ip What is going on? Why is the documentation at odds with the code? W -- Why is the legal status of chardonnay different to that of cannabis? worik.stan...@gmail.com 021-

Errors in the wrong place and wrong format

My virtual host has errors redirected to: Worik.errors.log (ErrorLog ${APACHE_LOG_DIR}/Worik.error.log) It is in this virtueal host that I have set-up mod-perl. Why then are errors sent to error.log? And why do errors emanating from mod_perl not have time stamps? -- Why is the legal status

Prototype mismatch

I get the following messages in my apache2/error.log when I restart. Why is that? What steps should I take to diagnose the problem? The line in the script where this ocures says: use FileHandle; cheers Worik Prototype mismatch: sub Apache::AdMachine::Track::LOCK_UN: none vs () Prototype

Re: $r->path_info unreliable?

On 19/06/14 14:11, Jie Gao wrote: > * Worik Stanton wrote: > >> Date: Thu, 19 Jun 2014 12:13:10 +1200 >> From: Worik Stanton >> To: mod_perl list >> Subject: $r->path_info unreliable? >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/2010

Re: $r->path_info unreliable?

e it does work? I do not think I understand URI --> file name translation. Worik PS I am sorry I sent this message twice. It seemed to bounce from the list at my end, and I admit I got a bit confused and thought I had used an incorrect address. I emailed the list owner thinking I had fail

$r->path_info unreliable?

package I have exactly like this, but in this case $r->path_info is empty. I am stumped. Worik -- The only true evil is turning people into things Granny Weatherwax worik.stan...@gmail.com 021-1680650, (03) 4821804 A

Why is RecuestRec::path_info sometimes empty?

ge I have exactly like this, but in this case $r->path_info is empty. I am stumped. Worik -- The only true evil is turning people into things Granny Weatherwax worik.stan...@gmail.com 021-1680650, (03) 4821804 A

Re: Trouble with script execution

On 19/05/14 12:13, Brad Van Sickle wrote: > Yep you need to restart to see your changes. I am sure I read somewhere that mod_perl monitors scripts and reloads them if the modification date changes. But oh well. It definitely notices sometimes. cheers Worik -- The only true evil is turn

Re: What about debugging?

On 19/05/14 12:03, Worik Stanton wrote: > Is there a way to get useful debugging info? > > I am getting messages like: > > "failed to resolve handler `Apache::AdMachine::MyHandler;' > Excuse my sillieness. `Apache::AdMachine::MyHandler;' had a ';&#x

Re: Trouble with script execution

On 19/05/14 11:34, John Dunlap wrote: > No, you have to restart the server for code changes to be noticed. Does that mean I have to restart my server for every change to a script? Worik -- The only true evil is turning people into things Gra

What about debugging?

"failed to resolve handler `Apache::AdMachine::MyHandler;' I am a bit lost Worik -- The only true evil is turning people into things Granny Weatherwax worik.stan...@gmail.com 021-1680650, (03) 4821804 A

Trouble with script execution

ure what mod_perl is doing. There seems to be a time element. After restarting the server everything goes well for a while (minutes) but soon behaviour changes and I am back to only some of the code executing (with no oither changes but the passing of time). I thought mod_perl would reload code th

Re: API Docs

On 16/05/14 21:09, André Warnier wrote: > Maybe you should start here : > https://perl.apache.org/docs/2.0/user/handlers/intro.html#What_are_Handlers_ > Thank you. That is very useful Worik -- The only true evil is turning people in

Re: Testing mod_perl

and am making some progress. I have used the API today to get document_root (thank-you j...@lariat.co) and to filter by IP. cheers Worik > > > On Wed, May 14, 2014 at 5:01 PM, Worik Stanton wrote: > >> On another matter... >> >> On 15/05/14 05:16, Perrin Ha

Re: API Docs

as linked to now from the documentation at perl.apache.org. Now I can see what I was missing, a "handler" method from a registered module Worik > > - Perrin > > On Wed, May 14, 2014 at 7:52 PM, Worik Stanton > wrote: >> I am still trying to fathom the

Testing mod_perl

arly I am doing the wrong thing, no matter how natural it seems and I need some help to get on the right track cheers Worik -- The only true evil is turning people into things Granny Weatherwax worik.stan...@gmail.com

Re: Trouble with mod_perl API: E.g., Apache2::Directive::conftree()

On 15/05/14 05:16, Perrin Harkins wrote: > Hi Worik, > > Your ErrorLog question isn't really a mod_perl issue, but I'd suggest > you check for warnings at startup. You may not have APACHE_LOG_DIR > defined, etc. > The ErrorLog issue only happens under mod_perl. Giv

API Docs

ous, what is the context here I do not get? cheers Worik -- The only true evil is turning people into things Granny Weatherwax worik.stan...@gmail.com 021-1680650, (03) 4821804 Aotearoa (New Zealand) signature.

Trouble with mod_perl API: E.g., Apache2::Directive::conftree()

May 14 12:13:43 2014] -e: Use of uninitialized value $documentroot in concatenation (.) or string at /home/worik/Worik.org/cgi/track line 11. [Wed May 14 12:13:43 2014] -e: $documentroot '' at /home/worik/Worik.org/cgi/track line 11. in the logs. I copied the code from https://perl.apache.o