handler question
Hello, Is it possible, if yes then how, to set handler recursively for one directory? Now my handler is defined: SetHandler perl-script PerlHandler MyServ::MyHandler But if i try to access /my_server/some/other/dir then apache gives error because this directory doesn't exist, which is ok, because i want these some/other/dir to become parameters for my handler (not directories where files are), but how to make that apache won't check if directory exists or not. One possibility is to make these directories and in httpd.conf define same handler for all them but this ain't good. Rgds, Viljo
Re: RFC: Logging used Perl Modules (was Re: API Design Question)
James G Smith <[EMAIL PROTECTED]> said something to this effect on 07/02/2001:
> How would something like this do:
>
> NAME
>
> Apache::Use
>
> SYNOPSIS
>
> use Apache::Use (Logger => DB, File => "/www/apache/logs/modules");
>
> DESCRIPTION
>
> Apache::Use will record the modules used over the course of the
> Perl interpreter's lifetime. If the logging module is able, the
> old logs are read and frequently used modules are automatically
> loaded. Note that no symbols are imported into packages.
You can get this information from %INC, can't you? e.g.:
use Time::Local;
use Data::Dumper;
use Apache;
warn map sprintf("%-20.20s\t%s\n", $_, $INC{$_}), keys %INC;
Exporter.pm /usr/local/perl/5.6.0/Exporter.pm
Carp.pm /usr/local/perl/5.6.0/Carp.pm
XSLoader.pm /usr/local/perl/5.6.0/i686-linux/XSLoader.pm
mod_perl.pm /usr/local/perl/site_perl/5.6.0/i686-linux/mod_perl.pm
strict.pm /usr/local/perl/5.6.0/strict.pm
Apache/Connection.pm/usr/local/perl/site_perl/5.6.0/i686-linux/Apache/Connection.pm
Time/Local.pm /usr/local/perl/5.6.0/Time/Local.pm
Apache/Table.pm /usr/local/perl/site_perl/5.6.0/i686-linux/Apache/Table.pm
DynaLoader.pm /usr/local/perl/5.6.0/i686-linux/DynaLoader.pm
overload.pm /usr/local/perl/5.6.0/overload.pm
Apache/Constants/Exp
/usr/local/perl/site_perl/5.6.0/i686-linux/Apache/Constants/Exports.pm
AutoLoader.pm /usr/local/perl/5.6.0/AutoLoader.pm
Apache/Server.pm/usr/local/perl/site_perl/5.6.0/i686-linux/Apache/Server.pm
Data/Dumper.pm /usr/local/perl/5.6.0/i686-linux/Data/Dumper.pm
Apache.pm /usr/local/perl/site_perl/5.6.0/i686-linux/Apache.pm
Isn't this more or less what you mean?
(darren)
--
My studies in Speculative Philosophy, metaphysics, and science are all
summed up in the image of a mouse called man running in and out of every
hole in the Cosmos hunting for the Absolute Cheese.
-- Edmund Burke
Re: handler question
Viljo Marrandi <[EMAIL PROTECTED]> said something to this effect on 07/03/2001: > Hello, > > Is it possible, if yes then how, to set handler recursively for one > directory? Now my handler is defined: > > > SetHandler perl-script > PerlHandler MyServ::MyHandler > Use a Location rather than Directory directive. Use the absolute URI relative to the server as the second part (e.g., http://www.foo.bar/baz would look like ). Take a look at http://httpd.apache.org/docs/mod/core.html#location> and http://httpd.apache.org/docs/mod/core.html#directory>. > But if i try to access /my_server/some/other/dir then apache gives error > because this directory doesn't exist, which is ok, because i want these > some/other/dir to become parameters for my handler (not directories > where files are), but how to make that apache won't check if directory > exists or not. One possibility is to make these directories and in > httpd.conf define same handler for all them but this ain't good. If sounds like you want to use r->path_info in your application, so you *can't* create these directories, or they will become part of r->filename, not r->path_info. (darren) -- My mother always used to tell me, "The early bird gets the worm." The message seemed pretty clear to me: If you sleep late, you're a lot less likely to be killed by a bird. -- Elliott Downing
[DIGEST] mod_perl digest 2001/06/30
-- mod_perl digest June 24, 2001 - June 30, 2001 -- Recent happenings in the mod_perl world... Features o mod_perl status o module announcements o mailing list highlights o links mod_perl status o mod_perl - stable: 1.25 (released January 29, 2001) [1] - development: 1.25_01-dev [2] o Apache - stable: 1.3.20 (released May 15, 2001) [3] - development: 1.3.21-dev [4] o Perl - stable: 5.6.1 (released April 9, 2001) [5] - development: 5.7.1 [6] module announcements o AxKit::XSP::PerForm - a "magic" forms library for building complex web applications [7] o HTML::Template 2.3 - makes using HTML templates simple and natural by extending standard HTML with a few new HTML-esque tags [8] mailing list highlights o Long thread of the week goes to a discussion on how to layout a web application API. [9] It ended with an idea about how to optimize via Autosplit/Autoload and an module that records module statistics [10]. There is now a module RFC available for comment [11] o While not mod_perl related, here's a tidbit on how to create a script that uses Netscape cookies when crawling [12] o As usual, the dev list is buzzing with activity [13] news o Netcraft June statistics Apache 63.02% IIS 20.38% [14] o Security Space June statistics Apache 59.84% IIS 28.42% [15] 11.80% (224,373) of Apache servers are running mod_perl [16] links o The Apache/Perl Integration Project [17] o mod_perl documentation [18] o mod_perl modules on CPAN [19] o mod_perl homepage [20] o mod_perl news and advocacy [21] o mod_perl list archives [22] [23] happy mod_perling... --Geoff [EMAIL PROTECTED] -- [1] http://perl.apache.org/dist/ [2] http://perl.apache.org/from-cvs/modperl/ [3] http://www.apache.org/dist/httpd/ [4] http://dev.apache.org/from-cvs/apache-1.3/ [5] http://www.cpan.org/src/stable.tar.gz [6] http://www.cpan.org/src/devel.tar.gz [7] http://forum.swarthmore.edu/epigone/modperl/gralgulwhy [8] http://forum.swarthmore.edu/epigone/modperl/glilyyzhend [9] http://forum.swarthmore.edu/epigone/modperl/farkhimshe [10] http://marc.theaimsgroup.com/?l=apache-modperl&m=99405069123641&w=2 [11] http://marc.theaimsgroup.com/?l=apache-modperl&m=99410809405360&w=2 [12] http://forum.swarthmore.edu/epigone/modperl/mowhonhum [13] http://marc.theaimsgroup.com/?l=apache-modperl-dev&r=1&w=2&b=200106 [14] http://www.netcraft.com/survey/ [15] http://www.securityspace.com/s_survey/data/200106/index.html [16] http://www.securityspace.com/s_survey/data/man.200106/apachemods.html [17] http://perl.apache.org [18] http://perl.apache.org/#docs [19] http://www.cpan.org/modules/by-module/Apache/ [20] http://www.modperl.com [21] http://www.take23.org [22] http://forum.swarthmore.edu/epigone/modperl/ [23] http://marc.theaimsgroup.com/?l=apache-modperl&r=1&w=2
Re: handler question
> Use a Location rather than Directory directive. Use the absolute > URI relative to the server as the second part (e.g., > http://www.foo.bar/baz would look like ). Hey, that's what i needed. Thanks :) > If sounds like you want to use r->path_info in your application, > so you *can't* create these directories, or they will become part > of r->filename, not r->path_info. Actually i thought about r->uri. It returns everything after servername and if i split it using '/' as separator i think i'm almost there ;o). Or are there any reasons i shouldn't use r->uri? Rgds, Viljo
Re: RFC: Logging used Perl Modules (was Re: API Design Question)
darren chamberlain <[EMAIL PROTECTED]> wrote:
>James G Smith <[EMAIL PROTECTED]> said something to this effect on 07/02/2001:
>> How would something like this do:
>>
>> NAME
>>
>> Apache::Use
>>
>> SYNOPSIS
>>
>> use Apache::Use (Logger => DB, File => "/www/apache/logs/modules");
>>
>> DESCRIPTION
>>
>> Apache::Use will record the modules used over the course of the
>> Perl interpreter's lifetime. If the logging module is able, the
>> old logs are read and frequently used modules are automatically
>> loaded. Note that no symbols are imported into packages.
>
>You can get this information from %INC, can't you? e.g.:
Most definitely. However, you lose information about which
modules are needed more often than others. There's no difference
between all scripts needing CGI.pm and one script needing
Foo::Bar.
We also lose timing information. If 90% of the modules are
loaded into the process with the last request before the child is
destroyed, there's no point in loading them during the
configuration phase. We can help this a little by taking
snapshots of %INC at regular intervals (at the end of each
request, for example).
The current code I have uses %INC, but I wanted to write
something like the following:
sub use : immediate {
# do stuff here if logging
return CORE::use(@_);
}
--
James Smith <[EMAIL PROTECTED]>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix
Re: handler question
Viljo Marrandi <[EMAIL PROTECTED]> said something to this effect on 07/03/2001: > > If sounds like you want to use r->path_info in your application, > > so you *can't* create these directories, or they will become part > > of r->filename, not r->path_info. > > > Actually i thought about r->uri. It returns everything after > servername and if i split it using '/' as separator i think i'm > almost there ;o). Or are there any reasons i shouldn't use > r->uri? It depends on what you are trying to accomplish, of course, but for most purposes, yeah, splitting r->uri on '/' will give a useful list of directories. If you are using these as actual filenames, and ignoring r->filaname, however, beware of requests like: http://foo.bar.baz/my_hander/../../../../../../../etc/passwd which might be trying to get you to send your /etc/passwd. If you are using the URI to dispatch the request to a particular Perl module, take a look at Apache::Dispatch. (darren) -- The more we disagree, the better the chance that one of us is right.
Re: RFC: Logging used Perl Modules (was Re: API Design Question)
James G Smith <[EMAIL PROTECTED]> said something to this effect on 07/03/2001:
> darren chamberlain <[EMAIL PROTECTED]> wrote:
> > James G Smith <[EMAIL PROTECTED]> said something to this effect on 07/02/2001:
> > > Apache::Use
> >
> > You can get this information from %INC, can't you? e.g.:
>
> Most definitely. However, you lose information about which
> modules are needed more often than others. There's no difference
> between all scripts needing CGI.pm and one script needing
> Foo::Bar.
Good point.
> We also lose timing information. If 90% of the modules are
> loaded into the process with the last request before the child is
> destroyed, there's no point in loading them during the
> configuration phase. We can help this a little by taking
> snapshots of %INC at regular intervals (at the end of each
> request, for example).
>
> The current code I have uses %INC, but I wanted to write
> something like the following:
>
> sub use : immediate {
> # do stuff here if logging
> return CORE::use(@_);
> }
To go OT here, what would 'immediate' be doing here, if Perl
supported it?
(darren)
--
The three most dangerous things are a programmer with a soldering
iron, a manager who codes, and a user who gets ideas.
using XML::Parser with apache/modperl ???
hi question: is it possibly (should certainly be) to use the perl XML::Parser module with apache/modperl?? - - i ran into some problems trying this, here is what happened: i installed expat and the XML::Parser onto my macosx/darwin machine (perl 5.6.0, apache 1.3.19). when i run a CGI (it makes use of XML::Parser which uses EXPAT, a XMLparser C-library ) under my apache/mod_perl server it generates an error saying: dyld: /usr/sbin/httpd multiple definitions of symbol _XML_DefaultCurrent /usr/sbin/httpd definition of _XML_DefaultCurrent /Library/Perl/darwin/auto/XML/Parser/Expat/Expat.bundle definition of _XML_DefaultCurrent - apache vs. expat conflict as it seems the CGI script runs fine in the tcsh-shell on first try i only removed the /Library/Perl/darwin/auto/XML/Parser/Expat/Expat.bundle but of course this makes it worse saying: --- [Tue Jul 3 15:27:30 2001] [error] PerlRun: `Can't locate loadable object for module XML::Parser::Expat in @INC (@INC contains: /System/Library/Perl/darwin /System/Library/Perl /Library/Perl/darwin /Library/Perl /Library/Perl /Network/Library/Perl/darwin /Network/Library/Perl /Network/Library/Perl /usr/ /usr/lib/perl) at /Library/Perl/darwin/XML/Parser.pm line 15 Compilation failed in require at /Library/Perl/darwin/XML/Parser.pm line 15 during global destruction. BEGIN failed--compilation aborted at /Library/Perl/darwin/XML/Parser.pm line 19 during global destruction. Compilation failed in require at /Library/Perl/Create_Sentence.pm line 4 during global destruction. BEGIN failed--compilation aborted at /Library/Perl/Create_Sentence.pm line 4 during global destruction. Compilation failed in require at /Library/Perl/Speak.pm line 5 during global destruction. [Tue Jul 3 15:27:30 2001] [error] Can't locate object method "uri" via package "Apache::PerlRun" at /System/Library/Perl/darwin/Apache/PerlRun.pm line 212 during global destruction. -- obviously i cant remove /usr/sbin/httpd ...well its the apache server... any ideas? cheers christian
Re: RFC: Logging used Perl Modules (was Re: API Design Question)
On Tuesday 03 July 2001 16:46, darren chamberlain wrote:
> James G Smith <[EMAIL PROTECTED]> said something to this effect:
> > The current code I have uses %INC, but I wanted to write
> > something like the following:
> >
> > sub use : immediate {
> > # do stuff here if logging
> > return CORE::use(@_);
> > }
>
> To go OT here, what would 'immediate' be doing here, if Perl
> supported it?
It would run, well, immediately :) C is run before the rest of the code
(apart from BEGIN blocks) which is why one can't overload it (now) iirc.
--
___
Robin Berjon <[EMAIL PROTECTED]> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
---
In which level of metalanguage are you now speaking?
Re: RFC: Logging used Perl Modules
darren chamberlain <[EMAIL PROTECTED]> wrote:
>James G Smith <[EMAIL PROTECTED]> said something to this effect on 07/03/2001:
>> sub use : immediate {
>> # do stuff here if logging
>> return CORE::use(@_);
>> }
>
>To go OT here, what would 'immediate' be doing here, if Perl
>supported it?
It would be run at compile time when the compiler ran into it
instead of waiting for run-time. Basically, the following
invocations of &foo and &bar would be equivalent. The
`immediate' modifier could wrap an implicit BEGIN { } around any
invocation of the subroutine.
sub bar { do something; }
sub foo : immediate {
bar(@_);
}
foo($a, $b);
BEGIN {
bar($a, $b);
}
This is used in FORTH to support such things as if-then-else and
do-while constructs since they are just entries in the dictionary
like any other definition. FORTH actually uses it to build up
the entire language since there are no reserved words.
--
James Smith <[EMAIL PROTECTED]>, 979-862-3725
Texas A&M CIS Operating Systems Group, Unix
Re: using XML::Parser with apache/modperl ???
one thing you might need to do is compile apache without its expat build in as per Matt S.'s suggestion on axkit.org http://axkit.org/faq.xml look for 'I install AxKit and Apache segfaults when it starts' Christian Wattinger wrote: > > hi > > question: is it possibly (should certainly be) to use > the perl XML::Parser module with apache/modperl?? > - > - > i ran into some problems trying this, here is what > happened: > > i installed expat and the XML::Parser onto > my macosx/darwin machine (perl 5.6.0, apache 1.3.19). > > when i run a CGI > (it makes use of XML::Parser which uses EXPAT, a XMLparser C-library ) > under my apache/mod_perl server it generates an error saying: > > > dyld: /usr/sbin/httpd multiple definitions of symbol _XML_DefaultCurrent > > /usr/sbin/httpd definition of _XML_DefaultCurrent > /Library/Perl/darwin/auto/XML/Parser/Expat/Expat.bundle definition of > _XML_DefaultCurrent > - > > apache vs. expat conflict as it seems > > the CGI script runs fine in the tcsh-shell > > on first try i only removed the > /Library/Perl/darwin/auto/XML/Parser/Expat/Expat.bundle > but of course this makes it worse saying: > > --- > [Tue Jul 3 15:27:30 2001] [error] PerlRun: `Can't locate loadable object > for module > XML::Parser::Expat in @INC (@INC contains: /System/Library/Perl/darwin > /System/Library/Perl > /Library/Perl/darwin /Library/Perl /Library/Perl > /Network/Library/Perl/darwin /Network/Library/Perl > /Network/Library/Perl /usr/ /usr/lib/perl) at > /Library/Perl/darwin/XML/Parser.pm line 15 > Compilation failed in require at /Library/Perl/darwin/XML/Parser.pm line 15 > during global destruction. > BEGIN failed--compilation aborted at /Library/Perl/darwin/XML/Parser.pm line > 19 during global destruction. > Compilation failed in require at /Library/Perl/Create_Sentence.pm line 4 > during global destruction. > BEGIN failed--compilation aborted at /Library/Perl/Create_Sentence.pm line 4 > during global destruction. > Compilation failed in require at /Library/Perl/Speak.pm line 5 during global > destruction. > [Tue Jul 3 15:27:30 2001] [error] Can't locate object method "uri" via > package > "Apache::PerlRun" at /System/Library/Perl/darwin/Apache/PerlRun.pm line 212 > during global destruction. > -- > > obviously i cant remove > /usr/sbin/httpd > ...well its the apache server... > > any ideas? > > cheers > christian
Re: using XML::Parser with apache/modperl ???
Christian Wattinger <[EMAIL PROTECTED]> wrote: >hi > >question: is it possibly (should certainly be) to use >the perl XML::Parser module with apache/modperl?? I don't know about OS X, but my experience on OpenBSD requires Apache and XML::Parser be compiled with the same expat library. Either have Apache link against the system installed lib (which Perl most likely links against for XML::Parser) or change the RULE_EXPAT rule in src/Configuration (or similarly named file) to RULE_EXPAT=no. Details may vary a bit from system to system, but the goal is the same: Apache and XML::Parser using the same expat lib. -- James Smith <[EMAIL PROTECTED]>, 979-862-3725 Texas A&M CIS Operating Systems Group, Unix
Re: using XML::Parser with apache/modperl ???
On Tuesday 03 July 2001 18:06, Christian Wattinger wrote: > question: is it possibly (should certainly be) to use > the perl XML::Parser module with apache/modperl?? It is, though you need to compile with --disable-rule=EXPAT. Mod_perl should do that for you though. > when i run a CGI > (it makes use of XML::Parser which uses EXPAT, a XMLparser C-library ) > under my apache/mod_perl server it generates an error saying: > > > dyld: /usr/sbin/httpd multiple definitions of symbol _XML_DefaultCurrent > > /usr/sbin/httpd definition of _XML_DefaultCurrent > /Library/Perl/darwin/auto/XML/Parser/Expat/Expat.bundle definition of > _XML_DefaultCurrent > - > apache vs. expat conflict as it seems In my experience when that happens it just segfaults. But then maybe it doesn't work the same way under osx. Try disabling expat to see if it makes a difference. Also, have a look at the corresponding item there http://axkit.org/faq.xml (in any case, you should probably be using AxKit anyway ;-) -- ___ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com --- In which level of metalanguage are you now speaking?
Re: handler question
Hi!
On 3 Jul 2001, at 15:21, Viljo Marrandi wrote:
> Actually i thought about r->uri. It returns everything after servername
> and if i split it using '/' as separator i think i'm almost there ;o).
I have a nearly finished module which applies some regular
expression (specified in some config file) to the URI and puts the
stuff it found into $r->param (that means you have to use CGI or
Apache::Request to use it).
e.g: http://www.somehost.org/stuff/order_byname/id0099.html
Regexes:
order=>'order_(\w+)'
id=>'id(\n+)\.html'
After running the URL through my module you could get at the id
with $r->param('id')
If you're interested, I could send it to you ...
BTW, if anybody else is interested in this module, I could put it on
CPAN (after deciding on a Namespace etc)
--
D_omm
O_xyderkes http://domm.zsi.at
M_echanen
M_asteuei
Re: handler question
On Tuesday 03 July 2001 21:18, Thomas Klausner wrote: > I have a nearly finished module which applies some regular > expression (specified in some config file) to the URI and puts the > stuff it found into $r->param (that means you have to use CGI or > Apache::Request to use it). > > BTW, if anybody else is interested in this module, I could put it on > CPAN (after deciding on a Namespace etc) Pretty cool ! You should definitely put it on CPAN. Apache::RegexedParam ? -- ___ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com --- To err is human, to purr feline.
Re: handler question
All This is an interesting idea, so I thought I'd add my two cents and say that you can already do exactly this with mod_rewrite. I guess it's useful to have a perl module that does it as well, but sometimes re-inventing the wheel is not worth the trouble. I can see the utility for people who haven't got mod_rewrite... but still, it's small, fast and works beautifully with mod_perl. >I have a nearly finished module which applies some regular >expression (specified in some config file) to the URI and puts the >stuff it found into $r->param (that means you have to use CGI or >Apache::Request to use it). > >e.g: http://www.somehost.org/stuff/order_byname/id0099.html >Regexes: >order=>'order_(\w+)' >id=>'id(\n+)\.html' > Something like this will do it: RewriteRule ^/stuff/order_([^/]+)/id([^\.]+).html$ /some/handler?order=$1&id=$2 [QSA] Just wanted to let everyone know. Kyle Dawkins Systems Engineer Central Park Software, Inc. http://www.centralparksoftware.com
RE: handler question
> -Original Message- > From: Robin Berjon [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 03, 2001 3:42 PM > To: [EMAIL PROTECTED] > Subject: Re: handler question > > > On Tuesday 03 July 2001 21:18, Thomas Klausner wrote: > > I have a nearly finished module which applies some regular > > expression (specified in some config file) to the URI and puts the > > stuff it found into $r->param (that means you have to use CGI or > > Apache::Request to use it). > > > > > BTW, if anybody else is interested in this module, I could put it on > > CPAN (after deciding on a Namespace etc) > > Pretty cool ! just make sure that it follows the typical model of being as generic and portable as possible. looks like another mod_rewrite derivitave to me, though :) it would be really neat if it supported both CGI.pm and Apache::Request (though if you have to choose the latter is probably prefered ;) > You should definitely put it on CPAN. > Apache::RegexedParam ? Apache::URIToParam? --Geoff
Re: handler question
Robin Berjon <[EMAIL PROTECTED]> said something to this effect on 07/03/2001: > On Tuesday 03 July 2001 21:18, Thomas Klausner wrote: > > I have a nearly finished module which applies some regular > > expression (specified in some config file) to the URI and puts the > > stuff it found into $r->param (that means you have to use CGI or > > Apache::Request to use it). > > > > > BTW, if anybody else is interested in this module, I could put it on > > CPAN (after deciding on a Namespace etc) > > Pretty cool ! You should definitely put it on CPAN. Apache::RegexedParam ? How is it different from mod_rewrite using the QSA flag to add values to r->args? (This is a question, not a criticism!) (darren) -- Don't sweat the petty things, and don't pet the sweaty things.
Re: handler question
On Tuesday 03 July 2001 22:18, darren chamberlain wrote: > Robin Berjon <[EMAIL PROTECTED]> said something to this effect on 07/03/2001: > > Pretty cool ! You should definitely put it on CPAN. Apache::RegexedParam > > ? > > How is it different from mod_rewrite using the QSA flag to add > values to r->args? (This is a question, not a criticism!) Full blown Perl regexen ? Possibility to also replace the regex with a coderef and get real fancy ? Just off the top of my head. I'm not lobbying for this module to exist, I don't need it personally. But I like small and useful wheels. Plus, I'd prefer to do that kind of rewriting closer to the code that uses the params than the light front-end's httpd.conf is. -- ___ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com --- Give a man a fish and he will eat for a day. Teach him how to fish, and he will sit in a boat & drink beer all day.
Module::Use 0.02 uploaded
The uploaded file Module-Use-0.02.tar.gz has entered CPAN as file: $CPAN/authors/id/J/JS/JSMITH/Module-Use-0.02.tar.gz size: 2917 bytes md5: 96c3d47fb65b1f392626b082cf6ad85d No action is required on your part Request entered by: JSMITH (James G Smith) Request entered on: Wed, 04 Jul 2001 02:42:28 GMT Request completed: Wed, 04 Jul 2001 02:42:59 GMT The name was changed from Apache::Use due to the general nature of the code. It does not depend on Apache/mod_perl to work. Feel free to test and offer suggestions. If there are data stores that you would like to see work with this, then either mention them or contribute a module for them :) +-- James Smith - [EMAIL PROTECTED] | http://www.jamesmith.com/ [EMAIL PROTECTED] | http://cis.tamu.edu/systems/opensystems/ +--
Jobs
In case you didn't see it already, then there's a nice pile of mod_perl related jobs posted at http://jobs.perl.org/ You can get a list of the mod_perl related ones at http://www.take23.org/jobs/ or (if your browser supports javascript) at http://perl.apache.org/jobs.html - ask -- ask bjoern hansen, http://ask.netcetera.dk/ !try; do();
mod_perl on win2k: cannot load module
I am a currently trying to have Apache and mod_perl to run with win 2000. This is part of a review being currently undertaken by my company on what technical solution to use for our intranet web server. I have installed Apache 1.20 downloaded from apache.org web site. I have installed Perl from Activestate. The version installed is ActivePerl-5.6.1.626-MSWin32-x86-multi-thread. I have downloaded mod_perl from ftp://theoryx5.uwinnipeg.ca, installed it using ppm. The version of the package I have installed is mod_perl-1_25_1_3_20-eapi.tar.gz Unfortunately, I have trouble running mod_perl: when I start Apache, I get the following error message: "Syntax error on line 204 of c:/apache/apache/conf/httpd.conf: Cannot load c:/apache/apache/modules/mod_perl.so into server: (127) The specified procedure could not be found:" I have some questions. Thanks for any information that could be provided: 1) Would anyone know what causes this error message and what I could do to solve the issue? 2) What is the difference between the eapi and no eapi versions of mod_perl. I have tried both, without success. I get an error message complaining about API in the version of mod_perl that does not have eapi in its name. 3) In the mailing list and at other places on the net, reference is made of expat_win32.dll. What is this dll for? Do I need it? Raphael __ Voila vous propose une boite aux lettres gratuite sur Voila Mail: http://mail.voila.fr
Re: mod_perl on win2k: cannot load module
Try download ApacheModulePerl.dll from www.cpan.org, choose by author, Jeffrey_Baker good luck - Frans Electronics Engineering Department of Electrical Engineering Institut Teknologi Bandung Email: [EMAIL PROTECTED] - On Wed, 4 Jul 2001, [EMAIL PROTECTED] wrote: > I am a currently trying to have Apache and mod_perl to run with win 2000. This is >part of a review being currently undertaken by my company on what technical solution >to use for our intranet web server. > > I have installed Apache 1.20 downloaded from apache.org web site. > I have installed Perl from Activestate. The version installed is >ActivePerl-5.6.1.626-MSWin32-x86-multi-thread. > I have downloaded mod_perl from ftp://theoryx5.uwinnipeg.ca, installed it using ppm. >The version of the package I have installed is mod_perl-1_25_1_3_20-eapi.tar.gz > > Unfortunately, I have trouble running mod_perl: when I start Apache, I get the >following error message: >"Syntax error on line 204 of c:/apache/apache/conf/httpd.conf: > Cannot load c:/apache/apache/modules/mod_perl.so into server: (127) The specified >procedure could not be found:" > > I have some questions. Thanks for any information that could be provided: > 1) Would anyone know what causes this error message and what I could do to solve the >issue? > 2) What is the difference between the eapi and no eapi versions of mod_perl. I have >tried both, without success. I get an error message complaining about API in the >version of mod_perl that does not have eapi in its name. > 3) In the mailing list and at other places on the net, reference is made of >expat_win32.dll. What is this dll for? Do I need it? > > Raphael > __ > Voila vous propose une boite aux lettres gratuite sur Voila Mail: > http://mail.voila.fr > > >
