Ged Haywood wrote:
> [EMAIL PROTECTED]:~/src/mod_perl-1.29$ cat makepl_args.mod_perl
> EVERYTHING=1
> DO_HTTPD=1
> USE_APACI=1
> [EMAIL PROTECTED]:~/src/mod_perl-1.29$
> =
>
> I'd be happy to give it a spin with differen
Hi Joachim,
On Tue, 14 Oct 2003, Joachim Feise wrote:
> I was trying your configuration, and then tried several permutations, and
> found the problem: whenever USE_APACI is missing or USE_APACI=0, the
> resulting httpd segfaults.
> For example, with
> perl Makefile.PL DYNAMIC=1 EVERYTHING=1 or
>
Hi Philippe/Stas,
When I downloaded
http://perl.apache.org/dist/mod_perl-1.0-current.tar.gz
I saw it was still 1.28. Is it on purpose ?
However http://perl.apache.org/download/index.html
shows the version as 1.29
Sreeji
--- "Philippe M. Chiasson" <[EMAIL PROTECTED]> wrote: >
The URL
>
>
ht
Hi -- I have a site which mananges photos for
visitors. I log cookies to a log file using the
recipe from
http://perl.apache.org/docs/2.0/user/handlers/http.html#PerlLogHandler.
Here's the code
package CookLog;
use strict;
use warnings;
use Fcntl qw(:flock);
sub handler {
my $r = shift;
Thank you very nice!
Where should I have looked to figure this out myself?
At 11:00 PM -0400 10/13/03, Geoffrey Young wrote:
Matisse Enzer wrote:
Can I get access to PATH_TRANSLATED in a PerlRepsonseHandler?
if you're using the mod_perl API, you can get PATH_TRANSLATED by
joining $r->filename a
Udo Rader wrote:
hi,
we have some troubles with internal_redirect after upgrading to 1.99_10, here's what we try to do:
before mp 1.99_09 this line used to work:
---CUT---
$r->internal_redirect( $r->uri );
---CUT---
after upgrading to 1.99_10, we get the following in error_log:
-
Ideally, the cookie set by a request (be it an image or html)
originally sent to Site A should always be returned to any future
request to Site A. However, browsers now-a-days allow users to turn
off third party cookies - which may throw away any cookies from/to your core
site. Are you seeing this
Matisse Enzer wrote:
Thank you very nice!
Where should I have looked to figure this out myself?
if you're using the mod_perl API, you can get PATH_TRANSLATED by
joining $r->filename and $r->path_info.
from lots of places, like the eagle book and cookbook.
according to the docs,
calling $r
Geoffrey Young wrote:
Matisse Enzer wrote:
Thank you very nice!
Where should I have looked to figure this out myself?
[...]
also from the eagle book and cookbook, if you're familiar with the 1.0
API. I wasn't sure if this still worked in 2.0, however, but the docs I
mentioned are
http://per
Ged Haywood wrote:
>
> I think the docs could do with a patch... (hint:).
While it is of course trivial to patch the docs, I think that's the wrong
approach.
What's the point of an option that has to have a specific value?
If the USE_APACI=1 option is required, it no longer is an option and
shoul
Am Tue, 14 Oct 2003 18:20:29 + schrieb Stas Bekman:
> Udo Rader wrote:
>> hi,
>>
>> we have some troubles with internal_redirect after upgrading to 1.99_10, here's
>> what we try to do:
>>
>> before mp 1.99_09 this line used to work:
>>
>> ---CUT---
>> $r->internal_redirect( $r->ur
At 11:51 AM -0700 10/14/03, Stas Bekman wrote:
And if you have learned something on this list that is not
documented, documented but can't be found easily, remember that
patches are very welcome. If everyone who was helped here had
contributed back a doc patch, the docs would be in a much better
Matisse Enzer wrote:
At 11:51 AM -0700 10/14/03, Stas Bekman wrote:
And if you have learned something on this list that is not documented,
documented but can't be found easily, remember that patches are very
welcome. If everyone who was helped here had contributed back a doc
patch, the docs wou
On Sun, 2003-10-12 at 00:36, Shannon Eric Peevey wrote:
BTW, I have tested this modules against a Samba server that was only
allowing NTLMv2 connections with success. (I don't have access to a
win32 machine that I could test this against, so maybe...) Also, when
you run the test above, can
Sreeji K Das wrote:
Hi Philippe/Stas,
When I downloaded
http://perl.apache.org/dist/mod_perl-1.0-current.tar.gz
I saw it was still 1.28. Is it on purpose ?
However http://perl.apache.org/download/index.html
shows the version as 1.29
When did you do that? I have just tested and it fetches 1.29. Co
Udo Rader wrote:
we have some troubles with internal_redirect after upgrading to 1.99_10, here's what we try to do:
before mp 1.99_09 this line used to work:
---CUT---
$r->internal_redirect( $r->uri );
---CUT---
after upgrading to 1.99_10, we get the following in error_log:
-
Many thanks Hari.
Turns I was having an "acme.com" vs. "www.acme.com"
cookie descrepancy, and I didn't notice the obvious
until you reminded me.
I am glad it wasn't a mod_perl or apache oddity!
Curious: does scheme matter? That is,
can a cookie set by http://acme.com be read by
https://acme.c
Brian McCauley wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
- move the perl4 lib solution to the perl_reference.pod
Will do when I get round to that bit. I still think a mention of it
is needed in porting.pod to warn people away from it. If you disagree
simply delete the offending paragraph
Stas Bekman wrote:
came up with Apache::Filter::HTTPHeadersManip which you can try [snip]
If you have comments regarding the naming
then Ged Haywood wrote:
http://www.m-w.com/cgi-bin/dictionary?manipulate
I wonder if "Manip" would be better replaced by "Alter".
then Ruslan U. Zakirov wrote:
Vote f
19 matches
Mail list logo
