Il 25/05/2011 2.29, Cosimo Streppone ha scritto:
On Wed, 25 May 2011 02:20:23 +1000, André Warnier wrote:
marco wrote:
Il 24/05/2011 17.35, Adam Prime ha scritto:
On 11-05-24 11:30 AM, marco wrote:
Hi all,
I want to get the response time that Apache spends to serve a request
(from post-re
On Wed, 25 May 2011 02:20:23 +1000, André Warnier wrote:
marco wrote:
Il 24/05/2011 17.35, Adam Prime ha scritto:
On 11-05-24 11:30 AM, marco wrote:
Hi all,
I want to get the response time that Apache spends to serve a request
(from post-read-request phase to the response phase).
Any idea?
Torsten Förtsch wrote:
On Tuesday, May 24, 2011 18:20:23 André Warnier wrote:
Is it not easier to just read the Apache access log a posteriori, and
filter the lines which you need ?
With the appropriate LogFormat, you can have the microseconds needed
for each request.
With Apache2::ModLogConf
Il 24/05/2011 20.11, Torsten Förtsch ha scritto:
On Tuesday, May 24, 2011 19:02:50 marco wrote:
In httpd.conf file I have:
PerlPostReadRequestHandler Dir::touch #this script is well
executed PerlResponseHandler Dir::timediff#this
handler (below) is not executed!
On Tuesday, May 24, 2011 19:02:50 marco wrote:
> In httpd.conf file I have:
>
> PerlPostReadRequestHandler Dir::touch #this script is well
> executed PerlResponseHandler Dir::timediff#this
> handler (below) is not executed!!!
perhaps you forgot
SetHandler m
Il 24/05/2011 18.19, Torsten Förtsch ha scritto:
On Tuesday, May 24, 2011 17:30:33 marco wrote:
I want to get the response time that Apache spends to serve a request
(from post-read-request phase to the response phase).
PerlPostReadRequestHandler "sub {\
use Time::HiRes();
On Tuesday, May 24, 2011 18:20:23 André Warnier wrote:
> Is it not easier to just read the Apache access log a posteriori, and
> filter the lines which you need ?
> With the appropriate LogFormat, you can have the microseconds needed
> for each request.
With Apache2::ModLogConfig you can even ins
marco wrote:
Il 24/05/2011 17.35, Adam Prime ha scritto:
On 11-05-24 11:30 AM, marco wrote:
Hi all,
I want to get the response time that Apache spends to serve a request
(from post-read-request phase to the response phase).
Any idea?
Thanks
I'm pretty sure there are messages buried in the ar
On Tuesday, May 24, 2011 17:30:33 marco wrote:
> I want to get the response time that Apache spends to serve a request
> (from post-read-request phase to the response phase).
PerlPostReadRequestHandler "sub {\
use Time::HiRes(); \
use Apache2::Reque
Il 24/05/2011 17.35, Adam Prime ha scritto:
On 11-05-24 11:30 AM, marco wrote:
Hi all,
I want to get the response time that Apache spends to serve a request
(from post-read-request phase to the response phase).
Any idea?
Thanks
I'm pretty sure there are messages buried in the archives (from
On 11-05-24 11:30 AM, marco wrote:
Hi all,
I want to get the response time that Apache spends to serve a request
(from post-read-request phase to the response phase).
Any idea?
Thanks
I'm pretty sure there are messages buried in the archives (from torsten)
showing how to do this with $r->push
Hi all,
I want to get the response time that Apache spends to serve a request
(from post-read-request phase to the response phase).
Any idea?
Thanks
Hi Chris,
On Mon, Sep 27, 2010 at 9:41 AM, Chris Ray wrote:
> Hello, I'm having issues installing Apache::Request which has been asked for
> when I tried to build Apache::Template.
My recommendation at this point would be to stop using
Apache::Template. It's not maintained anym
pache2-apxs=/usr/bin/apxs2
It's not clear what error you are talking about?
Anyhow, I just meant to mention that, in order to install
Apache::Request on a non-standard installation of Apache, I had to use
this :
/home/perl/5.10/bin/perl Makefile.PL
--with-apache2-apxs=/home/httpd/2.2/
Hello, I'm having issues installing Apache::Request which has been asked for
when I tried to build Apache::Template. See below:
ch...@debian:~/Apache-Template-2.00_01$ perl Makefile.PL
Warning: prerequisite Apache2::Request 0 not found.
Writing Makefile for Apache::Template
When
This is a case of I'm pretty sure I saw this before but can't for the
life of me remember where -- so it might not even be possible.
I'm trying to access the values of the 'Order', 'Allow', and 'Deny'
apache directives, as they're set at request time, i.e. after merging.
Basically what I want to d
Patrick Galbraith wrote:
Hi all,
I'm in the midst of writing a book currently, and am covering the
sections in the book on mod_perl and Apache.
In previous texts for Apache 1.3, it
would show 11 phases. In the document on
http://httpd.apache.org/docs/2.2/developer/request.html, it shows 4
prima
Hi all,
I'm in the midst of writing a book currently, and am covering the
sections in the book on mod_perl and Apache.
In previous texts for Apache 1.3, it
would show 11 phases. In the document on
http://httpd.apache.org/docs/2.2/developer/request.html, it shows 4
primary phases, each having the
On Wed 17 Sep 2008, John ORourke wrote:
> I had the same problem but the machine serving the request had a
> reverse proxy in front of it. I used the following to inject a
> header on the proxy:
>
> SetEnv SCHEME http
> RewriteCond %{HTTPS} on
> RewriteRule ^(.*) $1 [E=SCHE
Torsten Foertsch wrote:
On Wed 17 Sep 2008, grsvarma019 wrote:
But , i couldn't find how to extract the protocol(http or https )
There are Apache2::ModSSL and Apache::SSLLookup on CPAN in case you need
that information in a request phase prior to the ResponseHandler.
I had the sam
On Wed 17 Sep 2008, grsvarma019 wrote:
> But , i couldn't find how to extract the protocol(http or https )
There are Apache2::ModSSL and Apache::SSLLookup on CPAN in case you need
that information in a request phase prior to the ResponseHandler.
Mod_ssl can be configured to export SSL informatio
On Wed, 17 Sep 2008 00:21:52 -0700 (PDT)
grsvarma019 wrote:
> But , i couldn't find how to extract the protocol(http or https )
> from the current URL using apache request object.
> Can you please anybody help me in this?
See: perldoc Apache2::RequestRec
# HTTP protocol
Hi,
I am using mod_perl for authentication.
I could able to extract the Host and path information of the currect URL
using apache request object.
like $apache->header_in(Host) and $apache->uri respectively.
But , i couldn't find how to extract the protocol(http or https ) from the
will need to run it under ModPerl::Registry.
> >
> > In your CGI script, while running under ModPerl::Registry., you even
> > have access to the request object. If, at main::, you have my $r = shift;,
> > then you will get the object.
> >
> > I hope this helps.
>
ed. While reading the mod_perl book, I noticed they are using
Apache::Request versus CGI for form data handling. Why is that? Is it
recommended to use Apache over CGI? Any advantages? I am using CGI because its
a standard module.
TIA
Disclaimer: Technically, I'm always wrong!!
-
Mag Gam wrote:
> I am bit confused. While reading the mod_perl book, I noticed they are
> using Apache::Request versus CGI for form data handling. Why is that? Is
> it recommended to use Apache over CGI? Any advantages? I am using CGI
> because its a standard module.
CGI.pm is old a
request object. If, at main::, you have my $r = shift;, then you
will get the object.
I hope this helps.
-Ants
Mag Gam <[EMAIL PROTECTED]> wrote: Hi All,
I am bit confused. While reading the mod_perl book, I noticed they are using
Apache::Request versus CGI for form data handling.
Hi All,
I am bit confused. While reading the mod_perl book, I noticed they are
using Apache::Request versus CGI for form data handling. Why is that? Is it
recommended to use Apache over CGI? Any advantages? I am using CGI because
its a standard module.
TIA
On 10/25/07, Yuri Pats <[EMAIL PROTECTED]> wrote:
> From some
> time (maybe some upgrade was done) all handlers that uses
> Apache2::Request, was broken.
Sounds like you should try recompiling libapreq2 then.
- Perrin
Good day.
Some strange thigs happens on my computer now.
I use mod_perl a lot. Sometimes I debug apps on my desktop. From some
time (maybe some upgrade was done) all handlers that uses
Apache2::Request, was broken.
Some simple example:
sub handler : method {
my ($self, $r) = @_;
2007/9/20, Philippe M. Chiasson <[EMAIL PROTECTED]>:
> lists user wrote:
> > I have another question,since we have modperl's full features,
>
> Depends on how you define full features ;-)
>
> > why we
> > need Apache::Request yet?
>
> It's called
lists user wrote:
> I have another question,since we have modperl's full features,
Depends on how you define full features ;-)
> why we
> need Apache::Request yet?
It's called Apache2::Request now for mod_perl 2. Main reason to want to
use it is to deal with client data. POST
I have another question,since we have modperl's full features,why we
need Apache::Request yet?
Thanks.
Let me clarify what I'm doing. I copied the docs folder in Apache::AuthCookie
and then dropped it in my 'DocumentRoot'. Then copied the sample module and
put in one of the paths of @INC. Tried it, and it worked like a charm except
that when the secured page was accessed, the perl script was render
hmmm... no luck still!
BTW, even trying Apache::AuthCookie 3.10 on Apache 1.3/ mod_perl 1.29 also
reports the same problem now!
Perrin Harkins wrote:
>
> On 5/25/07, _spitFIRE <[EMAIL PROTECTED]> wrote:
>> I'm now using Apache 2.0.59 / mod_perl 2.0.3 / Apache:AuthCookie 3.10
>>
>> However, I
On 5/25/07, _spitFIRE <[EMAIL PROTECTED]> wrote:
I'm now using Apache 2.0.59 / mod_perl 2.0.3 / Apache:AuthCookie 3.10
However, I now get the error
"Can't locate loadable object for module Apache::Constants"
You don't have to use mod_perl 2 to use the latest Apache-AuthCookie,
but if you
Perrin Harkins wrote:
>
> This problem you're seeing may be a result of long-ago changes in the
> mod_perl 1 API, or a bug in the old module that you're using.
>
> - Perrin
>
>
Thanks for the tip!
I'm now using Apache 2.0.59 / mod_perl 2.0.3 / Apache:AuthCookie 3.10
However, I now get th
On 5/25/07, _spitFIRE <[EMAIL PROTECTED]> wrote:
Sorry! I meant to say
Apache 1.3/ mod_perl 1.29 / apache-authcookie-1.4
I don't actually see Apache-AuthCookie 1.4 on CPAN or even backpan.
It must be pretty old. There is a note in version 2.011 which came
out 7 years ago about how to upgrade
Perrin Harkins wrote:
>
> Meaning mod_perl 1.30?
>
>> I tried to deploy the sample code given with AuthCookie-1.3
>
> Which module is this? There are many things on CPAN with AuthCookie
> in their names, but none of them are version 1.3.
>
> - Perrin
>
>
Sorry! I meant to say
Apache 1.3/
On 5/25/07, _spitFIRE <[EMAIL PROTECTED]> wrote:
Before I post my question, I would like to say this - "I'm new to mod_perl
and hence bear with my silly
questions!"
Welcome aboard, _spit.
I'm using Mac OSX 10.4.8/Apache 1.3
Meaning mod_perl 1.30?
I tried to deploy the sample code given
Hi all,
Before I post my question, I would like to say this - "I'm new to mod_perl
and hence bear with my silly
questions!". I'm using Mac OSX 10.4.8/Apache 1.3 . I want to currently
develop a perl object that I can use for authorization (using AuthCookie). I
tried to deploy the sample code giv
> Ok. that answers a ton.
>
> Word-for-word, that should be in the PerlGlue docs.
>
libapreq is great, but the docs are seriously lacking.
I implemented my own wrapper for it, but it required a lot of delving
into the Apache2/APR::Request code to figure out how to make it work.
Non-trivial to
On May 3, 2007, at 9:44 PM, Joe Schaefer wrote:
The "Unknown Error" string is operating system dependent. On
my linux box it would be reported as "Success", since the error
code in any case is 0. "Missing input data" comes from the
apreq ala APR::Request::Error::NODATA, and counts as a trivial
Jonathan Vanasco <[EMAIL PROTECTED]> writes:
> On May 3, 2007, at 9:19 PM, Joe Schaefer wrote:
>
>> Here's what I was alluding to on apreq-dev when you asked about it:
>
> that code makes sense...
>
> it makes me wonder more though:
>
> a)
> what's the deal with
> Missing input
On May 3, 2007, at 9:19 PM, Joe Schaefer wrote:
Here's what I was alluding to on apreq-dev when you asked about it:
that code makes sense...
it makes me wonder more though:
a)
what's the deal with
Missing input data
Unknown Error : 0
are thos
Jonathan Vanasco <[EMAIL PROTECTED]> writes:
> i'm standardizing my some functions to release into cpan and am at a bit of a
> loss on catching apreq errors.
Here's what I was alluding to on apreq-dev when you asked about it:
my $body = eval { $req->body };
if ($@) {
if ($@ == APR::R
Sorry, I don't know the answer.
My little testing on Solaris gives me similar results,
and I'd like to back up your request.
- Original Message -
From: "Jonathan Vanasco" <[EMAIL PROTECTED]>
To: "modperl mod_perl"
Sent: Thursday, May 03, 2007 3:09
I'm posting to mp , as this is perl-glue related.
as a note, I'm using OS X as a dev box , and apreq doesn't compile
right on it - so that might be the problem
-
i'm standardizing my some functions to release into cpan and am at a
bit of a loss on catching apreq errors.
I have this c
Sorry for the trouble,I've got it.It's '$r->get_remote_host'.
-Original Message-
>From: Jeff Pang <[EMAIL PROTECTED]>
>Sent: Sep 26, 2006 5:22 AM
>To: modperl@perl.apache.org
>Subject: How to get remote host address in Apache::Request
>
>H
Hello,list,
I want to get the remote client's IPs in Apache::Request like the method of
'$q->remote_host()' in CGI.pm.
Can you help me?Thank you.
--
Jeff Pang
NetEase AntiSpam Team
http://corp.netease.com
>
> Sorry, forgot to list that, yes using mp1.x and apache 1.3
> with embperl version 1.3.4. We have the latest cgi.pm (
> version 3.16 ).
>
Embperl 1.3.4 is really very old, this might not work with an up to date
Apache::Request and/or CGI.pm, but I don't know. I suggest
We actually tried upgrading that this morning with no success we are now
on cgi.pm version 3.16.
thanks,
blayne
Gerald Richter wrote:
Hello,
we have just installed Apache::Request ( libapreq ) and
suddenly all of our file uploads are breaking with a ' Setup
of CGI.pm failed: Malf
Sorry, forgot to list that, yes using mp1.x and apache 1.3 with embperl
version 1.3.4. We have the latest cgi.pm ( version 3.16 ).
thanks,
Blayne
Tom Schindl wrote:
I assume you are using mp1.x and apache1.3?
Tom
Blayne Bayer wrote:
Hello,
we have just installed Apache::Request
I assume you are using mp1.x and apache1.3?
Tom
Blayne Bayer wrote:
> Hello,
>
> we have just installed Apache::Request ( libapreq ) and suddenly all of
> our file uploads are breaking with a ' Setup of CGI.pm failed: Malformed
> multipart POST' error. We use embperl a
Hello,
>
> we have just installed Apache::Request ( libapreq ) and
> suddenly all of our file uploads are breaking with a ' Setup
> of CGI.pm failed: Malformed multipart POST' error. We use
> embperl and everything was working fine.
> Have been searching for a
Hello,
we have just installed Apache::Request ( libapreq ) and suddenly all of
our file uploads are breaking with a ' Setup of CGI.pm failed: Malformed
multipart POST' error. We use embperl and everything was working fine.
Have been searching for a solution but cannot find any. Do
>my %params = $r->method eq 'POST' ? $r->content : $r->args;
Why not parse both and merge them?
But I would just use Apache::Request or CGI - they work, the authors
have thought of things that we wouldn't, etc...
It should be easy to replace the part of your
use CGI ;-)
pure perl
Alan Bailward wrote:
> Hey all. I have an old system I inherited which is about 4000 lines
> of "pure" mod_perl under apache 1.3, not using apache::request at all.
> I've been asked to "just" add file upload capabilities.
>
> Loo
Hey all. I have an old system I inherited which is about 4000 lines
of "pure" mod_perl under apache 1.3, not using apache::request at all.
I've been asked to "just" add file upload capabilities.
Looking at it, I thought I could change the code to add
enctype="mu
Boysenberry Payne wrote:
> I used to have:
>
> my $r = Apache->request();
> $r->content_type("text/html");
> $r->send_http_header;
>
> It seems the MP2 syntax is now:
>
> $r = Apache2::RequestRec->new($c);
nope. try
my $r = Apache2::Req
I used to have:
my $r = Apache->request();
$r->content_type("text/html");
$r->send_http_header;
It seems the MP2 syntax is now:
$r = Apache2::RequestRec->new($c);
$r->content_type("text/html");
How do I get $c?
How do I send the http header now?
Th
Tom Schindl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Javier Alonso Sánchez schrieb:
In according to the documentation:
If you need your own body parsing the better idea would be to write an
InputFilter http://perl.apache.org/docs/2.0/user/handlers/filters.html
to parse the content
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Javier Alonso Sánchez schrieb:
> In according to the documentation:
>
> "The Apache2::Request module provides methods for parsing GET and POST
> parameters encoded with either application/x-www-form-urlencoded or
> multipart/form-data."
>
> Does only
In according to the documentation:
"The Apache2::Request module provides methods for parsing GET and POST
parameters encoded with either application/x-www-form-urlencoded or
multipart/form-data."
Does only work with these two body types?
Is there another way to get the body content and the header
I'be just subscribed to libapreq, I'll follow the question there.
El dj 14 de 07 del 2005 a les 11:49 -0400, en/na Philip M. Gollucci va escriure:
Forwarding to apreq-dev list. I might be a ble to look at this but not
until later.
Marc Gràcia wrote:
> Hi everybody, I think we've found
El dj 14 de 07 del 2005 a les 14:18 -0400, en/na Joe Schaefer va escriure:
Marc Gràcia <[EMAIL PROTECTED]> writes:
> The problem is the value of a post parameter ends with an accentued char
> (áó etc... I dont know if you can view that...) the full process dies in
> the
>
Marc Gràcia <[EMAIL PROTECTED]> writes:
> The problem is the value of a post parameter ends with an accentued char
> (áó etc... I dont know if you can view that...) the full process dies in
> the
>
> my $upload = $ar->upload($param);
>
> line and an Interna
Forwarding to apreq-dev list. I might be a ble to look at this but not
until later.
Marc Gràcia wrote:
Hi everybody, I think we've found a curious bug in libapreq2.
There's a snippet of code on we basically are processing all post
parameters from a request:
if ($req->request_me
Well, just forgot to say that "$ar" is the Apache2::Request.
El dj 14 de 07 del 2005 a les 11:08 +0200, en/na Marc Gràcia va escriure:
Hi everybody, I think we've found a curious bug in libapreq2.
There's a snippet of code on we basically are processing all post parameters from
Hi everybody, I think we've found a curious bug in libapreq2.
There's a snippet of code on we basically are processing all post parameters from a request:
if ($req->request_method() eq 'POST')
{
my $hay_uploads=0;
foreach my $param (keys %args)
Joel Stevenson <[EMAIL PROTECTED]> writes:
> Has anyone else observed this behavior? Does anyone know if this has
> been fixed in any of the later versions of libapreq2 ?
Yes and yes; 2.02-dev is absolutely ancient history.
Apache::Request is called Apache2::Request nowadays;
Hi,
I'm running into a problem with Apache::Request handling large POST
values on a RedHat ES 3 system using libapreq-2.02-dev and the RH rpm
package of apache (2.0.46-44.ent). The problem is that when a large
value (say a memo entered into a textarea box) is received
Apache::Request
Let me see if I can answer this one.
Your sample code does not use Apache::Request at all. by the way, in the
latest release of modperl RC5, Apache::Request is now renamed to
Apache2::Request. You probably can guess why.
If you wish to use the Apache::Request object, you need to first load
the
On Fri, Apr 29, 2005 at 01:56:20PM -0400, Geoffrey Young wrote:
>
> > [error] [client 127.0.0.1] failed to resolve handler `Jadevine::Hello':
> > Apache::Request: httpd must load mod_apreq.so first
>
> try adding
>
> LoadModule apreq_module modules/mod_apreq
se, if you can't you can't.
HTH
Angie
On 4/29/05, Stephen Quinney <[EMAIL PROTECTED]> wrote:
> I've been having problems with the Apache::Request module (from
> libapreq2) and mod_perl2 for a while now and I've not come up with a
> decent solution. I am using the
Stephen Quinney <[EMAIL PROTECTED]> writes:
> I have tried putting the "use" statements in every order imaginable
> without any joy so I'm not sure what the error is trying to get me to
> do to correct the problem.
It's a server-config issue. You need to add a
LoadModule apreq_module modules/
> [error] [client 127.0.0.1] failed to resolve handler `Jadevine::Hello':
> Apache::Request: httpd must load mod_apreq.so first
try adding
LoadModule apreq_module modules/mod_apreq.so
in your httpd.conf.
--Geoff
I've been having problems with the Apache::Request module (from
libapreq2) and mod_perl2 for a while now and I've not come up with a
decent solution. I am using the Debian packages but I didn't get a
response from the maintainer so I hope someone here can enlighten me.
This is
Hello,
Apache::Request ignores character sets. So if you use an utf8 encoded form
values returned by Apache::Request->param are not flagged as valid perl UTF8
strings.
You need to filter them through Encode::decode().
That's surely, euhm, suboptimal. Did anybody find a nice way to
* D. Hageman shaped the electrons to say...
You can get Apache::Request for mod_perl 2 from the apache website.
Please note that if you use the ->upload feature that you might want to
pull down a version out of svn as it is buggy in the released tarball.
Speaking of - when will there be anot
You can get Apache::Request for mod_perl 2 from the apache website.
Please note that if you use the ->upload feature that you might want to
pull down a version out of svn as it is buggy in the released tarball.
On Sun, 27 Mar 2005, Praveen Ray wrote:
Hi
Has Apache::Request been Ported to
Hi
Has Apache::Request been Ported to mod perl 2 yet? What is
the
recommended way to read Request Parameters under mod perl
2?
thx
- Praveen
__
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http
ok
> Checking for Params::Validate...ok
> Checking for Class::Container...ok
> Checking for Apache::Request...ok
>
> *** If you plan to use Mason with Apache::Filter
> you will need to install Apache::Filter 1.021 or newer.
> Warning: prerequisite Apache::Filter 1.021 not fou
son's requirements was Apache::Request, which
> >wasn't compatible with mod_perl2.
> >
> >Is this setup possible or should i stick to apache 1.3/mod_perl 1.27?
> >There Mason works like a charm with Apache::Request for perl in /usr/bin.
> >
> >Without Mason,
ht[1] the goal of Apache::Request was to mimic most of
the functions in CGI.pm. I know that Michael Peters (who is hopefully
reading this message and can speak for himself) had to do some extra
coding for his CGI::Application plugin[2] which uses the Apache::*
modules when running inside a mod_pe
to parse it.
Cool. One of the goals we have with apreq2 is to use apache's input
filters to transparently parse the data without actually consuming it.
So Apache::Request (or Apache2::Request, if we go that route) shouldn't
really need a similar module, because that's already bu
o parse it.
Cool. One of the goals we have with apreq2 is to use apache's input
filters to transparently parse the data without actually consuming it.
So Apache::Request (or Apache2::Request, if we go that route) shouldn't
really need a similar module, because that's already
just Storable'd to disk.
Rebuilding simple consists of setting the environment back again, and
replacing STDIN with a IO::Scalar to the previously captured data.
Adam
David Naughton wrote:
Has anyone implemented the equivalent of CGI::Capture for
Apache::Request? If not, I may want to implement
Has anyone implemented the equivalent of CGI::Capture for
Apache::Request? If not, I may want to implement it myself. However, I'm
fairly new to mod_perl, so maybe there's a completely different and
better way to solve my problem, in which case I would appreciate some
enlightenment.
My
Bart Lenoir wrote:
I've been building perl-5.8.6, httpd-2.0.53, mod_perl-2.0.0-RC4(static) and
HTML-Mason-1.28 in /usr/local on Linux 2.4 (Debian). Everything went fine
until one of the last of Mason's requirements was Apache::Request, which
wasn't compatible with mod_perl2.
Is this
Hi to all,
I've been building perl-5.8.6, httpd-2.0.53, mod_perl-2.0.0-RC4(static) and
HTML-Mason-1.28 in /usr/local on Linux 2.4 (Debian). Everything went fine
until one of the last of Mason's requirements was Apache::Request, which
wasn't compatible with mod_perl2.
Is this se
Thanks Randy,
My tired eyes missed the required Apache 1.3 in the rush to get everything else
in place. I imagine that WebWork was trying to move to mod_perl 1.29 at the
time. I've just been caught in the awful predicament of regressing to Apache
1.3 or hacking WebWork. (Ohh, the curse of op
;s writing the
> code. I'm installing WebWork2 (
> http://webwork.math.rochester.edu/ )
>
> I tried backing out to mod_perl 1.29, but that's asked for
> Apache 1.3!
>
> Still no guesses on when Apache::Request might be finished porting?
libapreq2 is still in a development stag
k.math.rochester.edu/ )
I tried backing out to mod_perl 1.29, but that's asked for Apache 1.3!
Still no guesses on when Apache::Request might be finished porting?
---
Boyd Duffee,Keele University Computer Science (01782) 583437
Computing Officer BScH, BOFH, tinLC, ROTFLMAO
> There are a few critical fixes related to cookie handling which haven't
> made
> it into an official "release" yet. I've also found a bug where
> Apache::Request used to let you set ->status(), but doesn't anymore.
off the absolute top of my head I
* John D Groenveld shaped the electrons to say...
I've had no problems so far with libapreq2-2.04-dev, but with light usage.
http://httpd.apache.org/apreq/>
$ /opt/apache2/perl-5.8.6/bin/perl -MApache::Request -le 'print
$Apache::Request::VERSION' 2.04-dev
There are a few crit
In message <[EMAIL PROTECTED]>, "B. Duffee" writes:
>Can anybody make a good guess on when the mod_perl 2 port of Apache::Request
>will be finished? I came a little unstuck installing from CPAN when I found t
>he
>versions weren't compatible and I'm wond
Hi there,
Can anybody make a good guess on when the mod_perl 2 port of Apache::Request
will be finished? I came a little unstuck installing from CPAN when I found
the
versions weren't compatible and I'm wondering if I should back off to mod_perl
1
or wait for the port.
thanks
You don't state which Version of mp you are using but
Yes you can in both generations, by using the
Apache::Table/APR::Table-Object.
I have not tested it but as far as I understand the docs
this could should work.
8<
use mod_perl;
my $apr = Apache::Request
the form is presented. If the parameter "submitted" is
> >> present, then I want to process the form. However, if the processing
> >> "fails", I want to re-run the script, but only after deleting the
> >> "submitted" parameter. In the CGI
1 - 100 of 247 matches
Mail list logo
