> "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
Matt> On 21 Apr 2000, (Randal L. Schwartz) wrote:
>> Just in case you missed it... (but notice, no instructions!):
>>
>> package Stonehenge::Reload;
Matt> Thanks!
Matt> When perl is your day job, instructions just get in the way (I gue
On 21 Apr 2000, (Randal L. Schwartz) wrote:
> Just in case you missed it... (but notice, no instructions!):
>
> package Stonehenge::Reload;
Thanks!
When perl is your day job, instructions just get in the way (I guess you
gathered that from XML::XPath's instructions - did my email help you
> "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
Matt> On 21 Apr 2000, (Randal L. Schwartz) wrote:
Matt> and I'd be
Matt> interested in seeing Stonehenge::Reload, but I don't fancy
Matt> searching the archives of this list (which you posted it to,
Matt> IIRC), and a central repository of
On 21 Apr 2000, (Randal L. Schwartz) wrote:
> Matt> and I'd be
> Matt> interested in seeing Stonehenge::Reload, but I don't fancy
> Matt> searching the archives of this list (which you posted it to,
> Matt> IIRC), and a central repository of all your mod_perl stuff would
> Matt> be nice.
>
> If
> "Matt" == Matt Sergeant <[EMAIL PROTECTED]> writes:
Matt> Speaking of Stonehenge::* modules - any chance you can put up a
Matt> repository of them on your web page - I just installed
Matt> Stonehenge::Pictures (which is very cool - but I'd like to
Matt> extend it to automatically do the thu
On 21 Apr 2000, (Randal L. Schwartz) wrote:
> Yes. The Stonehenge::DBILog that I put into WebTechniques last month
[snip]
Speaking of Stonehenge::* modules - any chance you can put up a repository
of them on your web page - I just installed Stonehenge::Pictures (which is
very cool - but I'd lik
> "John" == John Ingram <[EMAIL PROTECTED]> writes:
John> The problem is that I believe Apache is doing it's own internal request
John> for the static error page and displaying the contents of that page to
John> the user, in response to the request that they made for some other URL.
John> Fo
Hi,
I was thrilled when I started using the latest version of DBILogger,
especially when I found that I could set the HTTP_USER programmatically,
so I can log the name of the user with each entry, even though I'm using
CGI database authentication. Yippee!
My only concern right now is that I wou
