On Thu, 15 Mar 2001, Jauder Ho wrote:
Alright, it's crunch time (trying to help a coworker out) and I need
to pick up some XML parsing with perl fast. So if anyone here has some
good resources, they can point me at, it would be much appreciated.
The problem I am trying to solve is as
Francisco Ramiro Pereira wrote:
Greetings
When I run http://localhost/eg I got this:
?Forbidden
You don't have permission to access /eg/ on this server.
Apache/1.3.14 Server at royal.sisnetti.com.br Port 80?
When I run http://localhost/asp/sample it works well.
What I'm doing wrong.
Dear BigSofte,
You must have read my mind! I do *indeed* have a software product which
I would love to have your help in marketing!!!
It is called ListGuard-2.0 and is an intelligent agent which uses
heuristic pattern matching to detect spam mails and advertising and
purge them from mailing
Hi everyone,
OK, I have tried just installing it and praying, that didn't seem to
work, Clark Cooper suggested that there may be a problem with the versions
of XML::DOM and XML::Parser, I have tried an earlier version of XML::Parser
(2.23 rather than 2.3) and I am now using Apache::ASP
Hi,
I was just tidying up an old mod_perl script which had some ugly "use
vars qw(...);" lines in it which I thought I'd replace with "our ...;".
I realise this isn't always a good idea since "our" is not intended as a
replacement for "use vars", but its often OK and I thought it would be
in my
Dear All,
could someone tell me what permissions are required on .asp files at
the moment I have them set to 664 but I did wonder if they get read, or
executed.
TIA
--
Gareth Westwood,
_
All those who believe in telekinesis, raise my hand.
I almost had a psychic girlfriend but
not really answering your questions, but
Ragarding moving the "our()" statement out of the function --
--- Steve Hay [EMAIL PROTECTED] wrote:
(b) because I can't actually do what I just did above in my mod_perl
script!
Couldn't you, if you put the func's into a module and our()'d it
Hi
can anyone enlighten me on why apache is failing to build with Mod_perl.
Ive tested my apache sources which builds and installs fine as a vanilla
The version of perl i have is 5.6.0 with the bundle CPAN apache mods installed
Im configuring mod_perl with:
EVERYTHING=1
Hi,
I want to filter/process some files using my own
handler as:
Location /foo
SetHandler perl-script
PerlHandler Apache::Myprocessing
/Location
Now, beofre sending the output of above handler to browser, I want
to process it as normal server-parsed (i. e. apache should search
Gareth Westwood wrote:
Hi everyone,
OK, I have tried just installing it and praying, that didn't seem to
work, Clark Cooper suggested that there may be a problem with the versions
of XML::DOM and XML::Parser, I have tried an earlier version of XML::Parser
(2.23 rather than 2.3) and
-Original Message-
From: Surat Singh Bhati [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 16, 2001 1:56 PM
To: [EMAIL PROTECTED]
Subject: enable normal SSI for output of mod_perl script
Hi,
I want to filter/process some files using my own
handler as:
Location /foo
On Sat, 17 Mar 2001, Surat Singh Bhati wrote:
Once I generate someoutput or page using my handler, I want to
pass it to apache to process the #exec.
Apache::SSI does not support #exec and "PerlSSI disabled in DSO build"
I am using the DSO mod_perl.
Any solution?
Apache::SSI does
On Fri, 16 Mar 2001, Paul wrote:
not really answering your questions, but
Ragarding moving the "our()" statement out of the function --
--- Steve Hay [EMAIL PROTECTED] wrote:
(b) because I can't actually do what I just did above in my mod_perl
script!
Couldn't you, if you put the
Stas Bekman wrote:
our() and other perl5.6 new APIs are too early to be endorsed, as 5.6 is
not yet considered as a stable version for mod_perl production sites,
therefore the guide barely touches on it.
Would you recommend the use of perl5.6 with mod_perl? What you are
saying is making me
All
I have just uploaded Tie::DxHash v0.91 to CPAN. Tie::DxHash
preserves insertion order and allows duplicate keys.
What on earth for?? Well, this helps people who are using Perl
Sections (particularly with mod_rewrite) to construct more complex
rules. The module's synopsis illustrates
I found the solution. I had been using "Apache::Cookie-fetch", both
from an authen handler and from a request handler. I switched to
using "Apache::Cookie-parse" instead, and the segv went away.
The Apache::Cookie monster ought to scare that bug out of the code
though; no matter what, it
On Fri, 16 Mar 2001, Wim Kerkhoff wrote:
Stas Bekman wrote:
our() and other perl5.6 new APIs are too early to be endorsed, as 5.6 is
not yet considered as a stable version for mod_perl production sites,
therefore the guide barely touches on it.
Would you recommend the use of perl5.6
dougm 01/03/16 09:23:31
Modified:src/modules/perl modperl_callback.c modperl_callback.h
modperl_handler.c modperl_handler.h modperl_types.h
Log:
prototype the 3 pools in run_handlers() rather that use va_args,
so we can have a pool sooner rather than
dougm 01/03/16 21:59:45
modperl-2.0/xs/Apache/ServerUtil - New directory
dougm 01/03/16 22:03:38
Modified:lib/ModPerl Code.pm
src/modules/perl modperl_callback.c modperl_config.h
modperl_handler.c modperl_handler.h modperl_mgv.c
modperl_mgv.h
xs/Apache/RequestUtil
dougm 01/03/16 22:08:05
Modified:src/modules/perl modperl_cmd.c
Log:
make use of modperl_handler_array_ macros
Revision ChangesPath
1.2 +2 -2 modperl-2.0/src/modules/perl/modperl_cmd.c
Index: modperl_cmd.c
21 matches
Mail list logo
