Hi all,
I'm having this problem when I run a perl module at the root of my web
site. This is the snippet from httpd.conf:
SetHandler perl-script
PerlHandler Apache::BOSCIndex
Now, when I have a form on my web site that posts to, let's
On Fri, 21 Jan 2000, G.W. Haywood wrote:
> Why do so many people seem
> to insist on using a sledgehammer to crack a nut? Horses for courses,
> as we join our metaphors around here.
Ad-Hoc queries? :-) With specs that change like water flows I'd have a
very hard time giving up the relational as
Thanks Randy,
I must make an Apache::Session FAQ. It would have this question and the
one about semaphores on Solaris.
I could make Apache::Session has a deep understanding of the data
structure by having it compare the serialized hash before and after the
session activity. I wonder if that wo
Hi there,
On 21 Jan 2000, Fernando Rowies wrote:
> first: trying example 4-9 from eagle book the result is an unvarying
> behavior. Running for first time it display the banner randomly,
> then, when i reload the page, take another randomly, but the third
> or fourth reload, no more pick_randoml
That worked! But can you tell me why it worked?
Thanks
--
Nancy
On Fri, 21 Jan 2000, Chuck O'Donnell wrote:
> How about
>
> ErrorDocument 401 /error.html
>
> Thanks,
>
> Chuck
>
> On Thu, Jan 20, 2000 at 12:39:23PM -0800, Nancy Lin wrote:
> >
> > Hi
> >
> > I don't know if this is
> (with appropriate changes to unload DSOs after shutting down perl, of
> course).
>
> I still get memory leakage - that's not terribly surprising - but
> it is much
> less. It's on the order of about 24K/restart and is probably the fault of
> some module - my guts would be DBD::Pg. I'll play ar
someone can help me with those problems?
first: trying example 4-9 from eagle book the result is an
unvarying behavior. Running for first time it display the
banner randomly, then, when i reload the page, take another
randomly, but the third or fourth reload, no more
pick_randomly_the_image, it
Hello,
Finally, I've composed all the work I did this year about mod_proxy
functionality as a dynamic content cache, into one patchset.
This job was done during while developing and maintaining websites
produced by http://web.masterskaya.ru (sorry, we have no english
page yet). Those we
(with appropriate changes to unload DSOs after shutting down perl, of
course).
I still get memory leakage - that's not terribly surprising - but it is much
less. It's on the order of about 24K/restart and is probably the fault of
some module - my guts would be DBD::Pg. I'll play around with tha
All,
ok, I think I nailed down the problem...
given the uri translation (by either mod_rewrite or PerlTransHandler)
/ --> /perl-bin/test.cgi
the code below will, by default
parse cookies whose path matches /
but bake cookies whose path matches /perl-bin
adding
-path => "/",
to the new cook
Hi there,
On Fri, 21 Jan 2000, Stephen Anderson wrote:
> > So in the longer term, is there a reason the parent has to contain the
> > interpreter at all? Can't it just do a system call when it needs one?
>
> Well, remember that the interpreter itself will remain shared
> throughout, so there'
> I am building mod_perl-1.21 into apache_1.3.9 using apaci.
> I run the following commands under mod_perl-1.21 directory
> perl Makefile.PL EVERYTHING=1 APACHE_PREFIX=/usr/local/apache
> make
> make test
> make install
or
cd ../apache_x.x.x
make install
> Everything looks fin
> I get the following link error when I try to make apache_1.3.9 with
> mod_perl-1.21. Am I missing a library module?
Asghar, when you have problems with mod_perl, please first search the
archives! There is a big chance that someone else has already asked this
question. Thank you!
I did the
On Thu, Jan 20, 2000 at 10:15:33PM -0800, Perrin Harkins wrote:
> "G.W. Haywood" wrote:
> > On Thu, 20 Jan 2000, Perrin Harkins wrote:
> > > you can't guarantee your data will be in a consistent state without
> > > transactions or some other way to do atomic updates
> > [snip]
> > > (e.g. you're r
mod_perl 1.21
Apache 1.3.9
Solaris 2.5.1, Linux 6.0
Is this a good or bad idea?
I want to create an inheritable module based on Apache::Request mainly for
uploading files, then create individual PerlHandler modules for individual
page content.
If I do this, will the uploaded files end up increa
15 matches
Mail list logo