Title: RE: Persisting data across handlers
Ah! Though I don't have access to an Apache2::RequestRec object in the childinithander. Any way I can pass pnotes from there?
cheers,
vipul
-Original Message-
From: Jonathan Vanasco [mailto:[EMAIL PROTECTED]]
Sent: Thu 3/9/2006 11:57 PM
Hi All!
Thanks for your suggestions.
Here is the solution:
# set the location
$r->headers_out->set( Location => $CONFIG->{ACCESS_DENIED} );
return Apache2::Const::REDIRECT;
Regards,
Younes
Message d'origine
>Copie à: modperl_users List
>De: Jonathan Vanasco <[EMAIL PROTECTED]>
>Sujet:
Hi,
I'm trying to get an impression of the likelihood of an release 2.0.3 in
near future.
More specificly I need a bugfix, which was fixed in SVN r357236 and it
would be very nice if there was an official mod_perl release in time for
Debian Etch.
Anyone knows in which directions the wind blows w.
[please cc the modperl@perl.apache.org list on all list response threads]
Hi [EMAIL PROTECTED],
> Hi Fred!
> I'm wondering if there is a correct way to set a cookie in a
> PerlAccessHandler.
>
> I've tried something like:
> $r->headers_out->add('Set-Cookie' => $cookie);
> and even:
> $r->err_h
Hi Fred!
I'm generating the cookie with CGI::Cookie().
I think the problem is elsewhere.
>From a PerlResponseHandler, the method I described works,
but I got the problem within a PerlAccessHandler.
Should I delegate the cookie generation to the PerlResponseHandler?
Younes
Message d'origine--
I'm generating the cookie with CGI::Cookie().
I think the problem is elsewhere
>From a PerlResponseHandler, the method I described works,
but I got the problem within a PerlAccessHandler.
Should I delegate the cookie generation to the PerlResponseHandler ?
Younes
---Message d'origine
>Dat
> Hi Fred!
> I'm generating the cookie with CGI::Cookie().
> I think the problem is elsewhere.
>
> From a PerlResponseHandler, the method I described works,
> but I got the problem within a PerlAccessHandler.
> Should I delegate the cookie generation to the PerlResponseHandler?
I do my cookie hand
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi all,
i'm building modperl2-HEAD (r384821) from src on OSX 10.4.5, against
httpd-,apr- & apr-util HEAD(s) (r384701).
'make' now fails @:
...
cd "src/modules/perl" && make
cc -I/usr/ports/mod_perl_svn/src/modules/perl
- -I/usr/ports/mod_perl_
> modperl_constants.c:930: error: 'SATISFY_ALL' undeclared (first use in
> this function)
> modperl_constants.c:930: error: (Each undeclared identifier is reported
> only once
> modperl_constants.c:930: error: for each function it appears in.)
> modperl_constants.c:935: error: 'SATISFY_ANY' undecl
I've found large need to migrate from mysql to postgres
Are there any mod_perl specific things I should know about?
I'm not referring to SQL traits or DBI differences, but any little
tricks or odd things that might happen when using the pg dbi under
apache
thanks,
Jonathan
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi geoff,
>> suggestions?
>
> stick with 2.2.0?
heh. and for production, i do.
but, i'm trying to track/deal with the roller-coaster changes in httpd
... so 'work though it' is the goal.
> really, I fixed this error only to be pelted with an
On Mar 10, 2006, at 12:26, Jonathan Vanasco wrote:
I'm not referring to SQL traits or DBI differences, but any little
tricks or odd things that might happen when using the pg dbi under
apache
The only one I can think of (and my information might be severely out-
of-date) is that you can o
Vipul Ved Prakash wrote:
>
> Hi,
>
> I'd like to create an object in the PerlChildInitHandler and allow
> access to this object in various PerlResponseHandlers. What's the best
> way to do this?
>
> I created a bucket brigade in childinit and associated it with the child
> pool and put the obj
On Fri, 2006-03-10 at 13:13 -0800, David Wheeler wrote:
> The only one I can think of (and my information might be severely out-
> of-date) is that you can open a MySQL connection before Apache forks
> and have it still work in the children
I'm not sure where you got this idea, but don't do it.
Thanks, Philippe. For some reason I thought I had to use Apache's
memory management abstractions for this.
cheers,
vipul
> -Original Message-
> From: Philippe M. Chiasson [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 10, 2006 1:21 PM
> To: Vipul Ved Prakash
> Cc: modperl@perl.apache.
Vipul Ved Prakash wrote:
> Thanks, Philippe. For some reason I thought I had to use Apache's
> memory management abstractions for this.
Nope, in your case, you could have been thinking 100% in Perl mode.
Philippe M.
On Fri, 10 Mar 2006 15:26:41 -0500
Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> I've found large need to migrate from mysql to postgres
>
> Are there any mod_perl specific things I should know about?
>
> I'm not referring to SQL traits or DBI differences, but any little
> tricks or odd thing
On Fri, 2006-03-10 at 15:26 -0500, Jonathan Vanasco wrote:
> I've found large need to migrate from mysql to postgres
>
> Are there any mod_perl specific things I should know about?
Were you using transactions with MySQL? If not, you'll need to learn
about that, and probably use Apache::DBI to do
I was using InnoDB w/transactions in mysql, because i needed
transactions and I've used mysql a lot before.
i was using mysql4 fine, but came into some odd bug caused by
changing the collation of a table to ut8. the only way to get rid of
it was to uninstall all of mysql & the data, or m
Hi there!
I've tried everything I found (in mailing lists, suggestions, web doc)
to send cookie from a PerlAccessHandler, but without success.
Before giving up, I would like to have an answer from the mod_perl2
authors if it is possible.
Here is my http.conf dealing with that:
--
On Sat, 11 Mar 2006 02:42:20 +0100
yperl <[EMAIL PROTECTED]> wrote:
> I've tried everything I found (in mailing lists, suggestions, web doc)
> to send cookie from a PerlAccessHandler, but without success.
>
> Before giving up, I would like to have an answer from the mod_perl2
> authors if it is
Jonathan Vanasco wrote:
with mysql5 , they decided to make mysql easier for everyone by setting
a default to ignore errors and coerce the data into a valid format
MySQL has always done that. Being able to turn that off was one of the
big new features in MySQL 5.
it turns out that you ca
Jonathan Vanasco wrote:
> with mysql5 , they decided to make mysql easier for everyone by setting
> a default to ignore errors and coerce the data into a valid format
Not true, MySQL has always treated data that way, that's one of the reasons
many DBAs didn't take it seriously. Only in 5.0 did the
23 matches
Mail list logo
