Kevin A. McGrail wrote:
http://www.thoughtworthy.com/downloads/Apache-DBI-0.97-KAM-patch
Here's a list of the changes:
Patch June 29, 2005 - Thanks to Kevin A. McGrail (ThoughtWorthy Media,
Inc.)
- Added a feature 'Apache::AuthDBI->setProjID(1)' to set a Shared
Memory Project
Recently, I posted about a problem with AuthDBI under MP2 discovered during
testing. After much hair pulling, I have deduced the following:
During my testing of AuthDBI.pm, I used apache1 and apache2 and ran under
different users.
In doing so, I somehow left orphaned semaphore arrays and share m
On Wednesday 29 June 2005 20:33, Geoffrey Young wrote:
> patch applied and will be part of the next release. since it's the only
> change I might wait a little bit before getting it to CPAN, but probably
> not more than a week.
BTW, I have learned that the first arg to sub is not an Apache2::Requ
On Jun 29, 2005, at 2:04 PM, Chris Jacobson wrote:
$cookie->path("/foo/");
Changing my code to work in that fashion caused the 'domain'
problem to go away. I know this is not a real solution, but it will
avoid the bug until such time that it is fixed.
If you don't upgrade to the c
Scott Cain wrote:
Hello,
I know that a little while ago, Lincoln put out a new version of CGI.pm
to deal with API changes in mod_perl2. The question I have is this: if
I am using mod_perl2 RC4, what version of CGI.pm should I be using (or
does it not matter)?
Thanks,
Scott
You want CGI-3
Hello,
I know that a little while ago, Lincoln put out a new version of CGI.pm
to deal with API changes in mod_perl2. The question I have is this: if
I am using mod_perl2 RC4, what version of CGI.pm should I be using (or
does it not matter)?
Thanks,
Scott
--
---
Torsten Foertsch wrote:
> Hi Geoff,
>
> the following code:
>
>
>
>
>
>
>
> produces:
>
> MUST NOT BE PRINTED
> OK
>
> I believe, this wrong. The first sub must even not be called.
>
> The attached patch cures it. It contains 2 additional tests and an additional
> line in IncludeHook.xs
Hi Geoff,
the following code:
produces:
MUST NOT BE PRINTED
OK
I believe, this wrong. The first sub must even not be called.
The attached patch cures it. It contains 2 additional tests and an additional
line in IncludeHook.xs.
Torsten
--- IncludeHook.xs~ 2005-04-12 17:26:27.0 +
On Wed, 29 Jun 2005, Stephen Quinney wrote:
> I'm having a problem with Apache2::Cookie (2.05-dev) and
> mod_perl2 (1.999.23). No matter what order I specify the
> parameters in for a new cookie the path always gets set to
> the value for the domain.
[ .. ]
This should be fixed in the current svn
Stephen Quinney wrote:
I'm having a problem with Apache2::Cookie (2.05-dev) and mod_perl2
(1.999.23). No matter what order I specify the parameters in for a new
cookie the path always gets set to the value for the domain. Some
sample code:
my $cookie = Apache2::Cookie->new($r,
Stephen,
I have encountered this same problem (using 2.05-dev). The
'cheap-hack' workaround currently would be to do something like this:
my $cookie = Apache2::Cookie->new($r,
-name => $username,
-value => $se
I'm having a problem with Apache2::Cookie (2.05-dev) and mod_perl2
(1.999.23). No matter what order I specify the parameters in for a new
cookie the path always gets set to the value for the domain. Some
sample code:
my $cookie = Apache2::Cookie->new($r,
-name
We have the need to delete a specific Set-Cookie header found in the
reponse within a reverse proxy [Apache2, libapreq2, mod_perl2,
mod_proxy with an HTTP output filter]. Looking at the docs for
APR::Table [1] it doesn't appear that this is possible. Although you
can "unset" and "delete" based on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear members of the mod_perl list,
I did not find an elegant, robust way of checking for the mod_perl
version number. I propose an unelegant, robust way below for those
interested.
$ENV{MOD_PERL} is obviously not OK because the UNIX environment has
t
Members,
Plese let me know if anyone experience the following issue.
Regards,
Raja
On 6/28/05, raja agireddy <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have implemented modperl2.0, Apache2.0 and AuthenSmb0.72. I have
> modified AuthenSmb to include timeout conditions.
>
> Everthing works fine,
The mod_perl is use is built from the current fedora core 4 rpm.
When I run apxs I get /usr/include/httpd (which is correct).
I don't see the call to apxs anywhere (I looked int ModPerl:MM related code and
in Scoreboard). Where is it located?
Another issue I see if apr (apache runtime) is packa
16 matches
Mail list logo