hi...
the following registry script only prints "foo" for me using bleedperl...
my $r = shift;
$r->send_http_header('text/plain');
$r->print('foo');
print 'bar';
I think it started around the time Doug sent this message along, but I can't
be sure - it's definitely been a while, though. sorry i
>
> have you tied STDOUT ? it is only done for you if you SetHandler
> perl-script, SetHandler modperl does not tie STDOUT.
sorry, should have said this was 1.26-dev...
I looked for places where I might have tied STDOUT and forgot to set it
back, but didn't find any.
nevertheless, an explici
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 04, 2001 11:27 AM
> To: modperl-2.0 dev-list
> Subject: Apache::Registry design
>
>
> I'm planning to work on Apache::Registry for 2.0 and want to
> hear how it
> should be different from wh
> should be discussed here, but feel free to invite modperl@
> users to join
> the discussion. i'm sure there are more interested here than geoff
> already though.
and I'm not _that_ interested
;)
-
To unsubscribe, e-mail: [
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 07, 2001 4:57 AM
> To: modperl-2.0 dev-list
> Subject: RFC: Apache::Registry family re-design
>
>
> This is a proposal paper for Apache::Registry for mod_perl 2.0.
>
> The whole family of Apa
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 07, 2001 1:28 AM
> To: modperl-2.0 dev-list
> Subject: vs
>
>
> I was thinking that in 2.0 we could have two different <>
> configuration
> containers, where will replace the from 1.x, an
>
> May be I didn't complete my thoughts in words, but that the
> whole point of
> my idea: make the interface as flexible as possible, now the
> implementation is up to us, nothing prevents us from using OO and
> subclasses. It's just that you don't have hardcoded
> subclasses, you write
> th
>
> there is no Changes file yet :)
> speaking of which, i'd really like to see a generated
> ChangeLog like what
> php does. which has detail of each change made, which files
> are touched,
> etc. then Changes will be a summary of the ChangeLog for
> each release.
as brian mentioned at th
>
> > speaking of which, i'd really like to see a generated
> ChangeLog like what
> > php does. which has detail of each change made, which
> files are touched,
> > etc. then Changes will be a summary of the ChangeLog for
> each release.
>
> As I understand Geoff is taking care of that :)
>currently we just grab the apr_table_get implementation for
>APR::Table::get(). The problem is that if there is more than one value
>added for the same key, get() will return one of these values.
in 1.x this is only true in a scalar context (and is documented as such in
the Apache::Table doc
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 25, 2001 1:10 AM
> To: Philippe M . Chiasson
> Cc: Geoffrey Young; '[EMAIL PROTECTED] '
> Subject: Re: :Table::get implementation?
>
[snip]
>
>
>
> There is another performance issue with setvars I'm thinking about.
> Currently when you perform $r->dir_config I have to merge the
> directory
> and server configs and give you the new table. This may be very
> expensive. Now we could avoid this by doing a deeper merge at the
> configurat
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 25, 2001 9:10 AM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED] '
> Subject: Re: :Table::get implementation?
>
>
> Geoffrey Young wrote:
>
> >&g
> Well, I'm catching up with the guts of 1.x and 2.x at the same time,
> that's what I see in 1.x:
>
> SV *
> dir_config(r, key=NULL, ...)
> Apache r
> char *key
>
> ALIAS:
> Apache::Server::dir_config = 1
>
> so you can call dir_config on $r or $s if I understand
> cor
>
> well if they are aliased then they are literally the same
> function, right? so we're still not talking separate
> configs, since they point to the same data...
>
> I'm not through with my second bowl of coffee yet, though :)
ok, scratch that - I see the code now...
so, now I'm wonderi
> -Original Message-
> From: Philippe M . Chiasson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 02, 2001 3:48 AM
> To: [EMAIL PROTECTED]
> Subject: [Patch] Apache->module()
>
>
> Hi, this patch implements the Apache->module() functionnality
> with a few differences.
>
> Apache
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 04, 2001 5:18 AM
> To: modperl-2.0 dev-list
> Subject: why header_(in|out) are deprecated in 2.x?
>
>
> I know that gozer has implemented the deprecated
> header_(in|out), but why
> do we dep
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 04, 2001 9:27 AM
> To: Geoffrey Young
> Cc: modperl-2.0 dev-list
> Subject: Re: why header_(in|out) are deprecated in 2.x?
>
>
> Geoffrey Young wrote:
>
>
> actually, my suggestion (if it didn't come across well) was to scrap
>
> $r->header_out(foo => 'bar')
>
> entirely,
well, I didn't really mean that either. by scrap I meant deprecate, not
remove.
egads, I'll stop now - my peanut sized brain is full of string beans lately
instead of g
>> the shortcut
>>
>> $r->headers_out(foo => 'bar')
>>
>> is nice to have, but using set() on the object is more descriptive of
>> what
>> is really taking place, and may help clarify things for the end-user.
>
>maybe it's just me, but I think "call it with just the header name
>to read, add a val
hi all...
I just noticed today that for a few phases stacked perl handlers do not
behave like stacked C handlers.
for instance, if I have two stacked PerlAuthenHandlers and the first
returns OK, the second one runs anyway. if the second one returns DECLINED,
then the entire phase returns
>
> But since there are only a handfull of people working on
> mod_perl right now,
> would it really be THAT usefull?
I would think so. I've been compiling bleedperl, mod_perl, and apache from
CVS on a nightly basis for almost a year now. over that time I've caught a
few changes to bleedper
>
> > Also this shows that BEGIN block of startup.pl is running
> twice. I don't
> > think this is right. (BTW, people are still reporting this
> problem with
> > mod_perl 1.26!)
>
> it is right. and also right with 1.26, if modperl is built as a dso.
yeah, I remember the DSO caveat. ho
hey...
did something happen to the bleedperl implementation of AUTOLOAD last
night? my nightly recompile built ok, but the server won't start...
[Fri Sep 28 07:32:36 2001] [error] Unable to create sub named "" at
/src/modperl/blib/lib/Apache/Constants.pm line 23.
just FYI...
--Geoff
--
> -Original Message-
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 28, 2001 10:30 AM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: bleedperl problems on 1.26-dev...
>
>
> On Fri, 28 Sep 2
> -Original Message-
> From: Eric Cholet [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 27, 2001 7:53 AM
> To: [EMAIL PROTECTED]
> Subject: Multiple PostReadRequest handlers
>
>
> Is it possible to have several PostReadRequest handlers
> run for a request? I have an issue where I
>
> BTW, from perl571delta.pod:
>
>
> Anonymous temporary files are available without need to
> 'use FileHandle' or other module via
>
> open($fh,"+>", undef) || ...
>
> That is a literal undef, not an undefined value.
>
yeah, pretty cool. IIRC there was also talk of open ($fh, ">&foo
>
> if ($mtime > $Stat{$file}) {
> delete $INC{$key};
> # warn "Reloading $key\n";
> if (my $symref = $UndefFields{$key}) {
> #warn "undeffing fields\n";
> no strict 'refs';
> undef %{$symre
FYI...
> -Original Message-
> From: Arthur Bergman [mailto:[EMAIL PROTECTED]]
> Sent: Monday, October 01, 2001 3:09 PM
> To: [EMAIL PROTECTED]
> Subject: PXR, Perl Cross Reference
>
>
> Hi,
>
> I have setup a lxr of the perl source at
> http://nanisky.com/pxr/source/
> Enjoy!
>
> I h
> > nice. but that doesn't give you a filename like
> Apache::File->tmpfile
> > does, so we'd still need the old code for Apache::compat.
>
>
> why do you want to know the filename?
>
my ($filename, $fh) = Apache::File->tmpfile;
...
$r->set_content_length(-s $filename);
:)
--Geof
hi all...
well, I have a bit of time on my hand now... time to get into 2.0 :)
anyway, if someone has some tuits, this from api.txt seems easy
enough...
$r->as_string:
not yet implemented
so, if someone can tell me where this should go, that would be great
- it's been a while since Doug'
hi all...
I was wondering if any thought was given to designing mod_perl 2.0
with ISPs in mind. I know this issue has cropped up on modperl@ but
I've been thinking about it lots lately and have an idea (well, some
ramblings, anyway)...
there are lots of problems with allowing users to have
Stas Bekman wrote:
>
> Geoffrey Young wrote:
>
> > hi all...
> >
> > I was wondering if any thought was given to designing mod_perl 2.0
> > with ISPs in mind. I know this issue has cropped up on modperl@ but
> > I've been thinking about
Stas Bekman wrote:
>
> >>I think the first thing to lookat is how PHP builds the jail.
> >>
> >
> > two different issues, no? one is about normal cgi/registry scripts
> > and the other about accessing areas of the server through the API.
> >
> > but yes, registry scripts would need some sort of
hi guys...
here is a doc update for get_basic_auth_pw.
the discrepancy was noted in this thread:
http://marc.theaimsgroup.com/?t=10106888792&r=1&w=2
and spotted by, uh, "The Sapphire Cat" :)
--Geoff
Index: Apache/Apache.pm
===
will return a value that
+ought to be propagated back to the client (typically AUTH_REQUIRED).
The second return value will be the decoded password sent by the client.
($ret, $sent_pw) = $r->get_basic_auth_pw;
Geoffrey Young wrote:
>
> hi guys...
>
> here is a
Stas Bekman wrote:
>
> A "method handler" is now specified using the `method' sub attribute, e.g.
>
> sub handler : method {};
well, I submitted a patch to get this to work in 1.3. last I
remember, doug was looking it over to make sure it didn't have any
leaks.
you could always commit it, whi
Geoffrey Young wrote:
>
> Stas Bekman wrote:
> >
> > A "method handler" is now specified using the `method' sub attribute, e.g.
> >
> > sub handler : method {};
>
> well, I submitted a patch to get this to work in 1.3. last I
> remember, do
Doug MacEachern wrote:
>
> On Mon, 21 Jan 2002, Geoffrey Young wrote:
>
> > Stas Bekman wrote:
> > >
> > > A "method handler" is now specified using the `method' sub attribute, e.g.
> > >
> > > sub handler : method {};
>
Stas Bekman wrote:
> Doug MacEachern wrote:
>
>> On Mon, 21 Jan 2002, Stas Bekman wrote:
>>
>>
>>> A "method handler" is now specified using the `method' sub attribute,
>>> e.g.
>>>
>>> sub handler : method {};
>>>
>>> instead of 1.xx's
>>>
>>> sub handler ($$) {}
>>>
>>
>> there's no need to
here's a (very) brief explanation:
Index: mod_perl_method_handlers.pod
===
RCS file: /home/cvspublic/modperl/mod_perl_method_handlers.pod,v
retrieving revision 1.9
diff -u -r1.9 mod_perl_method_handlers.pod
--- mod_perl_method_handle
>
> HTML::Entities correctly turns \x8b into ‹ while Apache::Util leaves it
> untouched. That character is treated by certain buggy browsers as < and can
> thus be used to fake tags. Note that just because your browser isn't
> vulnerable (ie it doesn't buy the fakes h1) doesn't mean that the pro
>
> However I'm not sure your patch does the right thing re UTF-8, unless there's
> some magic involved that I'm not seeing :-/ I'm no expert on how to deal with
> UTF-8 in C (or even in Perl) but it looks like you're only addressing 8bit
> encodings.
ok, after some to and fro with robin over
Stas Bekman wrote:
>
> Geoffrey Young wrote:
>
> >>However I'm not sure your patch does the right thing re UTF-8, unless there's
> >>some magic involved that I'm not seeing :-/ I'm no expert on how to deal with
> >>UTF-8 in C (or eve
hi guys...
sorry for keeping down the 1.3 path - I'll get with the program
eventually...
I was playing around with Apache::RegistryNG and found what seems to
be a bug.
Apache::Registry and Apache::RegistryNG do not behave the same wrt
redirects.
with Apache::RegistryNG, the simple redirect scr
hi all...
someone was asking the other day on IRC about per-connection
cleanups. I figured that since ap_register_cleanup schedules stuff
based on pools that registering code based on the connection pool
would be easy enough, so I tried...
below is a patch that works. it is pretty much stole
Ask Bjoern Hansen wrote:
>
> perl 5.7.x snapsnot @ 14868, apache 1.3.23 and mod_perl 1.26.
>
> $ perl Makefile.PL DO_HTTPD=1 USE_APACI=1 APACHE_PREFIX=/usr/local/apache-perl
>EVERYTHING=1 && make && make test
>
> []
>
> letting apache warm up...\c
> Use of uninitialized value in string a
> >
> > Any clues?
>
> this has been an issue for months...
>
> http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=100167794404350&w=2
>
> I have no idea where to start...
sorry, I guess I also should have mentioned that, at the time, I was building both
mod_perl-cvs and
bleedperl nightly,
Doug MacEachern wrote:
>
> On 20 Feb 2002, Salvador Ortiz Garcia wrote:
>
> > I dunno Doug's plans for a new 1.x release yet.
>
> i know i've been saying this for a while, but i am planning to catch up
> soon. if anybody wants to start updating the ToDo file with available
> patches, outstandi
hi all...
we'll, I've gone through the ToDo and tried to organize it somewhat into a STATUS
file. here's
what we have so far
Available Patches (12)
bug reports that I was able to associate with an origination report and an available
patch
Needs Patch (26)
bug reports that have no patch
Ask Bjoern Hansen wrote:
> On Fri, 1 Mar 2002, Geoffrey Young wrote:
>
>
>>* $r->finfo problem with HTML::Mason::ApacheHandler
>>Report: http://marc.theaimsgroup.com/?l=apache-modperl&m=96854561311519&w=2
>>Status:
>>
Doug MacEachern wrote:
> looks great, +1 to add the new STATUS file and cvs remove ToDo.
> thanks!
done :)
no email yet, should be along shortly...
--Geoff
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Stas Bekman wrote:
>
> since we use 'our' in the autogenerated .pm files, requiring 5.6.1 is
> probably a good idea:
>
[snip]
> package $module;
> +require 5.6.1;
it probably doesn't matter, but isn't that format deprecated now? bleedperl reports
v-string in use/require non-portable at -
>
> Well, `require 5.6.1' won't be understood by Perl before 5.6.0. I
> don't think it's as much deprecated as not understood by the Perls
> we're trying to avoid.
actually, I was intrigued by the "non-portable" ness of the warning - I thought it
might mean that
5.6.1 wouldn't work on 5.6.1 o
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 02, 2002 12:38 AM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: modperl/eg README httpd.conf.pl perl_sections.txt
> perl_sections_2.txt perlio.pl registry.pl startup.pl test.pl
>
>
> ask
Stas Bekman wrote:
>
> [crossposting dev list, since it's relevant]
>
> one of the issues to be resolved on the new mod_perl site (read:
> documentation) is to provide a mechanism for generating the Changes and
> (optionally Contributors) list. With mod_perl 1.x source this has been
> done manua
hi all...
I was thinking today about the possibility of regional mod_perl mailing lists
- kinda like the way local perl mongers have their own lists to coordinate group
activities, post local jobs, and just keep in touch with others in their area
with similar interests.
before posting a
Stas Bekman wrote:
>
> Somebody at p5p was asking about problems with 5.7.3 and modperl 1.x.
> I've run make test and got a bunch of failures, though didn't get a
> chance to investigate.
with the AUTOLOAD stuff fixed, I'm back to compiling bleedperl and
mod_perl CVS nightly, though I don't play
hi all...
well, I thought I'd try to help give the 1.3 tree some forward momentum...
my thought is to run through the STATUS file and present all the available patches
for
review and incorporation into core, and I thought I'd start with one I was pretty
familiar
with :)
PerlSetEnv seems
Stas Bekman wrote:
>
> Threaded perl 5.8.0 (still 5.7.3 now) needs to be compiled with
> -D_GNU_SOURCE to get the _struct_crypt right. This breaks apache-1.3 build:
can you elaborate on this a bit - I wasn't able to follow all the
threads on all the lists, but I'm able to build the 1.3 tree just
Geoffrey Young wrote:
>
> Stas Bekman wrote:
> >
> > Threaded perl 5.8.0 (still 5.7.3 now) needs to be compiled with
> > -D_GNU_SOURCE to get the _struct_crypt right. This breaks apache-1.3 build:
>
> can you elaborate on this a bit - I wasn't able to follow
Doug MacEachern wrote:
>
> i'd like to get 1.27 out soon, esp. with 5.8.0 rc candidates coming out
> which don't work with 1.26. as always, i'd appreciate any test reports
> of success and failure including perl -V, Makefile.PL options, etc. i put
> a snapshot (same as current cvs) here:
> http
Doug MacEachern wrote:
>
> i had a bad feeling about this. we should not be implementing escape_html
> to begin with, the functionality should all be in apache. i'm going to
> back out the patch.
sounds wise, especially considering people like Eric will end up with larger pages as a
result, w
> Test fails for me. I'll try and debug a bit more.
hmph, with the mod_perl.c patch?
does it fail for anyone else? I just rebuilt the 1.27 release candidate with 5.6.1
and it
passed just fine.
I rememebered that I forgot to include my build arguments in my last report, so maybe
that
will he
I'll be in my all day brainwashing session again today, so I'll have to look at
it tomorrow.
what I'm hoping is that the test is somehow not catching the right httpd.conf
setting or something, rather than mod_perl still being broken wrt PerlSetEnv -
all my live tests showed that the minor chan
ok, Matt, Eric, and I spent some time investigating this last week. here's the
summary:
- nobody else has been able to reproduce the test failure on their system
- Matt was able to verify that even though the test was failing the bug was not
apparent
on his system (via a quick handler and h
Stas Bekman wrote:
>
> This problem should be addressed before 1.27 is released. There are too
> many recurrent reports about it.
this should be fixed in current cvs
from cvs log lib/Apache/test.pm:
revision 1.23
date: 2001/08/26 18:29:55; author: dougm; state: Exp; lines: +1 -0
require URI
Doug MacEachern wrote:
>
> hopefully today. i'm doing some more testing, there's a snapshot here if
> anybody wants to test:
> http://perl.apache.org/~dougm/mod_perl-1.99_01-dev.tar.gz
>
> please report test results and perl -V if you have a chance. thanks.
I am having trouble with current CV
> > Yes, the bleadperl loses CFLAGS as reported by Doug at p5p. One of the
> > recent updates to MakeMaker broke things.
>
> has been fixed within patch level 15808
indeed :) nice work guys!
--Geoff
-
To unsubscribe, e-mail:
Stas Bekman wrote:
> there are taint mode problems with modperl-1.x and the latest
> bleadperl (testing with 15887).
>
> In addition to the taint bugs in Cwd that I'm trying to solve (see
> my report at p5p, including a partial patch), there is another
> taint problem when trying to st
Stas Bekman wrote:
> Geoffrey Young wrote:
>
>>
>>
>> Stas Bekman wrote:
>>
>> > there are taint mode problems with modperl-1.x and the latest
>> > bleadperl (testing with 15887).
>> >
>> > In addition to the taint
Per Einar Ellefsen wrote:
>
> Hi,
>
> After some discussion on the mod_perl list with Perrin Harkins, it
> seemed to me like it would be goot having a warning about problems with
> using constant subroutines (in hash constructs, where barewords get
> stringified, etc).
the warning looks g
>> personally, I think that FORBIDDEN() is just as bad as $FORBIDDEN -
>> it's removing the constant idea behind constant subroutines (though
>> sometimes you just have to do things that way to get past the compiler
>> or whatnot). it's a matter of personal choice, I suppose...
>
>
> Yes, I
Issac Goldstand wrote:
> Maybe I'm just tired, but I seem to be missing the question here... Can
> I bug either you to explain the issue a tad bit - even off list? Thanks.
>
> Issac
I think they're talking about this (and relevant p5p archive discussions from the same
time):
http://www.
hi guys...
Lyle brought this to my attention during some other offline discussions this
afternoon.
apparently, under mod_perl 1.3, $r->args(undef) doesn't work properly. to test,
just
add this line to your httpd.conf:
PerlInitHandler 'sub {shift->args(undef); return 0}'
and try ac
> So this:
>
> thing = (char*)((ST(1) == &sv_undef) ? NULL : pstrdup(p, SvPV(ST(1),na)))
>
> Probably intends to read:
>
> thing = (char*)((SvOK(ST(1))) ? pstrdup(p, SvPV(ST(1),na) : NULL)
>
cool! I integrated your new get_set_PVp logic and it worked just fine. nice work, and
Stas Bekman wrote:
> please test that 5.8.0 has no problems with Apache:: modules on your
> platforms/configs. 5.8.0-RC1 is to be released in 2 days.
>
> I've reinstalled a bunch of Apache:: modules that I usually have with
> 5.8.0-tobe and all were installed fine but these two:
>
> Apache:
> and come up with a
> "proper" example that does something more useful than simply illustrate
> how to use the api. my attempt at this was Apache::FormatText.
I've been using an interface to HTML::Clean (Apache::Clean on CPAN) to
illustrate filtering with Apache::Filter recently (both in th
>
> This is not possible with the current way Apache::Test configures
> things. Since mod_perl's config hooks are run after the rest of the
> configuration is done,
>
> Include "t/conf/extra.conf"
>
> will always come up before mod_perl startup and other perl files.
> Perhaps we need to fin
>
> and 2.0 doesn't have perl sections yet :(
>
>> any thoughts on using the blib pragma over the various use lib stuff
>> in modperl_inc.pl?
>
>
> I think we need to rethink the whole concept of how Apache::Test and its
> elements manipulate @INC. What are the demands from you Geoff, as it
[EMAIL PROTECTED] wrote:
> geoff 2002/08/07 12:39:00
>
> Modified:.STATUS
> Log:
> added bug report for print not looking at $\
the below patch seems to work, though I need to trace through the
rwrite_neg_trace() stuff to see what it actually does :) no
guarantees h
>
> people have problems with the Oracle DBD driver and 'SetHandler
> perl-script' See http://mathforum.org/epigone/modperl/lumfrahku
>
sorry, but I don't have the old thread in my inbox, so I can't reply
to it.
when you chose to print out ORACLE_HOME from Oracle.pm you were
actually look
>
> But Atsushi and the other guy with this problem were able to have this
> working under 'SetHandler modperl' that's the weird part, that makes me
> wonder why?
>
ok, I didn't catch that when I re-read the thread.
the order of Perl module loading between modperl and perl-script might
be
Tatsuhiko Miyagawa wrote:
> Here I've made a new mod_perl module which allows you to call
> ap_construct_url() from mod_perl.
>
> http://bulknews.net/lib/archives/Apache-CanonicalName-0.01.tar.gz
>
> Any suggestions welcome, especially regarding to:
>
> * Is naming OK?
>
> * Is it worth CPA
[EMAIL PROTECTED] wrote:
> dougm 2002/09/16 19:37:44
>
> Added: t/response/TestDirective pod.pm
> Log:
> Submitted by: Philippe M. Chiasson <[EMAIL PROTECTED]>
> Reviewed by:dougm
> test for pod directives
speaking of which, below is a test for testing all t
hi all...
today I took a stab at fixing a nit that's bothered me for a while...
$ make test TEST_VERBOSE=1
doesn't work with the Apache::Test stuff. I know I can run tests
individually with the -verbose flag, but I didn't see any reason why
Apache::Test can't follow the standard ExtUti
Doug MacEachern wrote:
>> return $preamble . <<'EOF';
>>+ifdef TEST_VERBOSE
>>+ override TEST_VERBOSE = -verbose
>>+endif
>
>
> pretty sure ifdef/endif/override/ifeq are not portable (gmake-isms)
ah, right.
>
> better to have the Makefile run 't/TEST -verbose=$(TEST_VERBOSE)'
>
> of c
I thought that Doug had mentioned a few times that this functionality
was a mistake in 1.0 and deprecated in 2.0. in fact, I thought it was
in the 2.0 docs someplace, but I couldn't find it.
it doesn't matter to me, but in the case that it doesn't belong in 2.0
proper it should probably make
hi doug...
I started poking around the compat.pm today in a few spare moments
and found
sub register_cleanup {
shift->pool->cleanup_register(@_);
}
sub post_connection {
shift->connection->pool->cleanup_register(@_);
}
but in 1.3 post_connection() is an alias for $r->register_cle
here's a patch for the post_connection() stuff I mentioned last week.
I also added a test, though neither really test much.
--Geoff
Index: t/response/TestCompat/request.pm
===
RCS file: /home/cvspublic/modperl-2.0/t/response/Test
hi...
I found it strange that hooks/authz.t didn't actually test the
PerlAuthzHandler - shuffling the test so that it actually tests the
hook in question is probably better (in theory at least :)
--Geoff
Index: t/hooks/TestHooks/authz.pm
scratch that - I see how it works now.
geez, this test autogenerate stuff is confusing :)
sorry for the waste of bandwidth...
Geoffrey Young wrote:
> hi...
>
> I found it strange that hooks/authz.t didn't actually test the
> PerlAuthzHandler - shuffling the test so that
hi all...
I had a few moments so I've started to port Apache::Clean over to
mod_perl 2.0. it's far from complete, and I haven't examined all the
issues with proper caching headers yet, but you can find the work in
progress here:
http://www.modperlcookbook.org/~geoff/modules/experimental/A
hi doug...
I've been playing around with Apache::Filter in 2.0 and found
something I don't understand.
if I call
$r->update_mtime($time);
$r->set_last_modified();
_after_ I read/write to the filter, the the Last-Modified header
doesn't get set properly by default_handler but if I
but in 1.3 post_connection() is an alias for $r->register_cleanup -
from what I can tell, 1.3 doesn't provide for per-connection cleanups
natively. did I miss something?
1.3 has a conn_rec.pool, it just isn't exposed to mod_perl.
yeah, that's what I meant :)
i think post_connection shoul
The URL
http://www.modperlcookbook.org/~geoff/modules/experimental/Apache-Clean-2.00b.tar.gz
has entered CPAN as
file: $CPAN/authors/id/G/GE/GEOFF/Apache-Clean-2.00b.tar.gz
size: 4725 bytes
md5: a25497718555ef6567bdd38685a6b940
it's still incomplete, but it should be educational at lea
hi all...
below is a patch, created (mostly) by darren, for functionality requested by a user.
basically, Martin has asked for single quotes to be automatically escaped by
escape_html(), alongside the other 4 escapes (<, >, &, "). see
http://marc.theaimsgroup.com/?t=10367907486&r=1&w=2
Stas Bekman wrote:
Stas Bekman wrote:
I'm going to release a first 2.0 module on CPAN. I'm wondering about the
top level namespace naming.
I think I beat you to it :)
http://search.cpan.org/author/GEOFF/Apache-Clean-2.00b/
here's a quick overview:
http://marc.theaimsgroup.com/?l=apache-m
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=103539781700876&w=2
You are using a streaming filter? So nothing would happen after you
finish the write loop, because the EOS bucket will cause the connection
filters to be called which will trigger the HEADERs filter to send the
header, e
ieving revision 1.78
diff -u -r1.78 Changes
--- Changes 6 Dec 2002 13:09:15 - 1.78
+++ Changes 6 Dec 2002 15:22:25 -
@@ -10,6 +10,8 @@
=item 1.99_08-dev
+add $r->as_string [Geoffrey Young]
+
add backcompat vars: $Apache::Server::CWD and
$Apache::Server::AddPerlVersion [Stas Bekman]
Ind
1 - 100 of 1378 matches
Mail list logo
