l/apriconv, mod_perl2, libapreq2.
The documentation at
http://perl.apache.org/docs/2.0/devel/debug/c.html#Debugging_Threaded_MPMs
refers to some links on debugging threads using gdb, but the pages do not
exist. Looks like these pages have moved:
4.10 Debugging Programs with Multiple Thr
* André Warnier wrote:
> Date: Sat, 17 May 2014 11:59:24 +0200
> From: André Warnier
> To: mod_perl list
> Subject: Re: API Docs
> User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
>
> Worik Stanton wrote:
> >On 16/05/14 21:09, André Warnier wrote:
>
Worik Stanton wrote:
On 16/05/14 21:09, André Warnier wrote:
Maybe you should start here :
https://perl.apache.org/docs/2.0/user/handlers/intro.html#What_are_Handlers_
Thank you. That is very useful
Welcome.
One thing which you cannot complain about apparently, is the number of answers
On 16/05/14 21:09, André Warnier wrote:
> Maybe you should start here :
> https://perl.apache.org/docs/2.0/user/handlers/intro.html#What_are_Handlers_
>
Thank you. That is very useful
Worik
--
The only true evil is turning people in
Remove me from the mail list please
Holger Kipp 於 2014年5月16日星期五寫道：
>
> Am 15.05.2014 um 01:52 schrieb Worik Stanton
>
> >:
>
> > I am still trying to fathom the API.
> >
> > I have struck a snag with the documentation.
> >
> >
> > https:
Am 15.05.2014 um 01:52 schrieb Worik Stanton :
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
> says
>
> use Apache2::Connection ();
> use A
Dear Worik,
Am 15.05.2014 um 01:52 schrieb Worik Stanton :
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
> says
>
> use Apache2::Connection ()
The $r there is the Apache2::RequestRec object. It gets passed to
your handler. See the handler example in the overview:
https://perl.apache.org/docs/2.0/user/intro/start_fast.html
- Perrin
On Wed, May 14, 2014 at 7:52 PM, Worik Stanton wrote:
> I am still trying to fathom the API.
>
&g
* Worik Stanton wrote:
> Date: Thu, 15 May 2014 11:52:39 +1200
> From: Worik Stanton
> To: mod_perl list
> Subject: API Docs
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
> Thunderbird/24.5.0
>
> I am still trying to fathom the API.
>
>
$r stands for the connection handle IMO.
Most like the $dbh in a database connection.
On Thu, May 15, 2014 at 7:52 AM, Worik Stanton wrote:
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apach
$r is a Apache2::RequestRec instance.
On Wed, May 14, 2014 at 7:52 PM, Worik Stanton wrote:
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
> says
>
>
> What is $r?
Handler context object:
<https://perl.apache.org/docs/2.0/user/intro/start_fast.html>
signature.asc
Description: PGP signature
I think it is a RequestRec object. But also I think it should be explicitly
stated.
On Thu, May 15, 2014 at 1:52 AM, Worik Stanton wrote:
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apach
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
> says
>
> use Apache2::Connection ();
> use Apache2::RequestRec ();
>
> my $c
Worik Stanton wrote:
I am still trying to fathom the API.
I have struck a snag with the documentation.
https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
says
use Apache2::Connection ();
use Apache2::RequestRec ();
my $c = $r->connection;
What is $r?
I
2014-05-15 1:52 GMT+02:00 Worik Stanton :
> I am still trying to fathom the API.
>
> I have struck a snag with the documentation.
>
>
> https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
> says
>
> use Apache2::Connection ();
> use Apach
On 15/05/14 23:55, Perrin Harkins wrote:
> The $r there is the Apache2::RequestRec object. It gets passed to
> your handler. See the handler example in the overview:
> https://perl.apache.org/docs/2.0/user/intro/start_fast.html
Thank-you.
That looks very useful. I can see where it w
I am still trying to fathom the API.
I have struck a snag with the documentation.
https://perl.apache.org/docs/2.0/api/Apache2/Connection.html#Synopsis
says
use Apache2::Connection ();
use Apache2::RequestRec ();
my $c = $r->connection;
What is $r?
I am missing something obvi
Thanks for the spot, update committed.
On Mon, Mar 18, 2013 at 9:51 AM, Torsten Förtsch
wrote:
> On 03/12/2013 02:59 AM, Martín Ferrari wrote:
>> +$r->write("ok 1");
>> +$r->write("not ok 2");
>
> I think it should read (missing \n):
>
> +$r->write("ok 1\n");
> +$r->write("not ok
On 03/12/2013 02:59 AM, Martín Ferrari wrote:
> +$r->write("ok 1");
> +$r->write("not ok 2");
I think it should read (missing \n):
+$r->write("ok 1\n");
+$r->write("not ok 2\n");
Torsten
Thanks, change applied r1457851.
On Mon, Mar 11, 2013 at 6:59 PM, Martín Ferrari
wrote:
> Hi,
>
> I was trying to set up a test environment for a mod_perl module, and
> -among many other problems I had with the docs, that I'll try to put
> in other reports-, I've foun
Hi,
I was trying to set up a test environment for a mod_perl module, and
-among many other problems I had with the docs, that I'll try to put
in other reports-, I've found some code that does not even compile,
and is missing required modules, under
http://perl.apache.org/docs/gener
On Tue, Feb 22, 2011 at 3:32 PM, Mark Hedges wrote:
> I copied this useful debugging filter at
> http://perl.apache.org/docs/2.0/user/handlers/filters.html#All_in_One_Filter
>
> It works fine, but I can't `perl -c` :
Yes, the modules that are built to run in the context of Ap
> I copied this useful debugging filter at
> http://perl.apache.org/docs/2.0/user/handlers/filters.html#All_in_One_Filter
>
> It works fine, but I can't `perl -c` :
>
> hedges@vm5:~/foo$ perl -c Lame.pm
> Invalid CODE attribute: FilterConnectionHandler at Lame
I copied this useful debugging filter at
http://perl.apache.org/docs/2.0/user/handlers/filters.html#All_in_One_Filter
It works fine, but I can't `perl -c` :
hedges@vm5:~/foo$ perl -c Lame.pm
Invalid CODE attribute: FilterConnectionHandler at Lame.pm line 26
BEGIN failed--compilation abort
http://perl.apache.org/docs/2.0/user/config/custom.html
The example under the heading 'Creating and Using Custom Configuration
Directives', if copied verbatim, produces the following error when you
run httpd -t:
Can't locate object method "MyOtherParameter"
Meant to cross-post this to the list.
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Software Engineer - TicketMaster - http://ticketmaster.com
1024D/A79997FA
no docs on
it.
Anyway, i have a problem with the line
/configure --with-module=filters:/path/to/httpd-apreq-2/env/mod_apreq.c
I found the file mod_apreq.c in libapreq2-2.04-dev /env but not in
libapreq2-2.06-dev.
Where is that file? Also previous file src/libapreq2.la is in /library/
directory
Searching for some clue of simultaneous static compilation of apache+mp2+apreq2
i have
only found this 2005-march entry in mailinglists.
> Has anyone managed to compile a static (no DSO) apache with mod_perl and
> libapreq? Both mod_perl and libapreq have instructions for building them
> statica
if you want the same
script to run under mp1 and mp2.
Look for Constants Co-Existance on the docs site.
--
END
What doesn't kill us can only make us stronger.
Nothing is impossible.
> I'm still a little curious if there are any pitfalls to having both
> installed on the same machine
there shouldn't be, provided you use a recent version and don't override the
checks in Makefile.PL.
--Geoff
On 10/15/05, Chris Winters <[EMAIL PROTECTED]> wrote:
> I've been scouring the MP2 docs but can't find out whether I can have
> MP1 and MP2 safely installed on the same machine. Does anything exist
> on this?
>
> Why I'm asking: I've got MP 1.29 and 2.0.2-R
I've been scouring the MP2 docs but can't find out whether I can have
MP1 and MP2 safely installed on the same machine. Does anything exist
on this?
Why I'm asking: I've got MP 1.29 and 2.0.2-RC2 installed, plus the
latest libapreq2. When trying to install libapreq 1.33 (for
just to let you know MX asf.osuosl.org. has broken policies, error report:
<<< 550 Dynamic IP Addresses See:
http://www.sorbs.net/lookup.shtml?219.192.112.121
It refuses mails from 219.192.112.121 just because it is dynamic IP.
Yes, it is dynamic IP and there is no problem with it. It is
900
Date: Wed, 21 Sep 2005 14:39:13 +0900
From: Jan Kratochvil <[EMAIL PROTECTED]>
To: Philip M. Gollucci <[EMAIL PROTECTED]>
Subject: Repost to mod_perl docs-dev
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="H1spWtNR+x+ondvy"
Matt Hahnfeld wrote:
> I was going through the filters documentation for mod_perl 2.0 here:
>
> http://perl.apache.org/docs/2.0/user/handlers/filters.html
>
> Under "All-in-one" filter, there's some source code for Dump.pm. Run
> on my system under mod_perl 2.
I was going through the filters documentation for mod_perl 2.0 here:
http://perl.apache.org/docs/2.0/user/handlers/filters.html
Under "All-in-one" filter, there's some source code for Dump.pm. Run
on my system under mod_perl 2.0.0 and Apache 2.0.54, it returns the
followin
Stas Bekman wrote:
Carl Johnstone wrote:
I'd suggest rewording the "answer" to something like:
In a URL which contains a query string, if the string has multiple
parts separated by ampersands and it contains a key named "reg", for
example http://example.com/foo.pl?foo=bar®=foobar
Hi Folks
>carl was saying that if you put a literal
>'http://example.com/foo.pl?foo=bar®=foobar' in your html _that_ is the
>cause of the problem - unescaped ampersands in url links are not allowed, so
>the literal url in user html should be
>'http://example.com/foo.pl?foo=bar®=foobar'.
Sorry,
On Tue, Apr 26, 2005 at 10:31:42AM -0400, Stas Bekman wrote:
>>> Since when unescaped & in the QUERY_STRING part of the URL are not allowed?
>> I dunno the specifics, but if you try using the w3c validator you end up
>> with something like this
>> reference not terminated by REFC delimiter
>> h
Carl Johnstone wrote:
I'd suggest rewording the "answer" to something like:
In a URL which contains a query string, if the string has multiple parts
separated by ampersands and it contains a key named "reg", for example
http://example.com/foo.pl?foo=bar®=foobar, then some browser
we commit something like the following? Or should we just nuke
the whole section altogether?
Index: src/docs/tutorials/client/browserbugs/browserbugs.pod
===
--- src/docs/tutorials/client/browserbugs/browserbugs.pod (revis
uld be nice so we can add that to the URL that started this
thread.
Here?
http://www.w3.org/TR/1999/REC-html401-19991224/appendix/notes.html#h-B.2.2
Thanks Steve,
So should we commit something like the following? Or should we just nuke
the whole section altogether?
Index:
Stas Bekman wrote:
>Geoffrey Young wrote:
>
>
>>>Since when unescaped & in the QUERY_STRING part of the URL are not allowed?
>>>
>>>
>>I dunno the specifics, but if you try using the w3c validator you end up
>>with something like this
>>
>> reference not terminated by REFC delimiter
>>
>>
Geoffrey Young wrote:
Oh, I see, I thought you were talking a bug in the docs building system.
But if you write:
'http://example.com/foo.pl?foo=bar®=foobar'.
There is no problem whatsover. Since there is no ® here.
exactly :)
Since when unescaped & in the QUERY_STRING part
> Oh, I see, I thought you were talking a bug in the docs building system.
>
> But if you write:
>
> 'http://example.com/foo.pl?foo=bar®=foobar'.
>
> There is no problem whatsover. Since there is no ® here.
exactly :)
>
> Since when unescaped
the actual userspace problem really is - the workaround
might work, but the underlying problem is that they don't properly escape
their ampersands in their own url links.
at least that's what I think carl was trying to say :)
Oh, I see, I thought you were talking a bug in the docs building
> Beg your pardon? Have you looked at the HTML source code? it goes:
>
> href="http://example.com/foo.pl?foo=bar®=foobar";>http://example.com/foo.pl?foo=bar®=foobar
I think what carl was saying was that the source of the bug in the
discussion was incorrect, not in how we render the page o
Geoffrey Young wrote:
Carl Johnstone wrote:
On:
http://perl.apache.org/docs/tutorials/client/browserbugs/browserbugs.html
It talks about browsers misreading URLs like:
http://example.com/foo.pl?foo=bar®=foobar
Presuming this is within a HTML page e.g.:
http://example.com/foo.pl?foo=bar®=foobar
Carl Johnstone wrote:
>
> On:
> http://perl.apache.org/docs/tutorials/client/browserbugs/browserbugs.html
>
>
> It talks about browsers misreading URLs like:
>
> http://example.com/foo.pl?foo=bar®=foobar
>
> Presuming this is within a HTML page e.g.:
>
>
On:
http://perl.apache.org/docs/tutorials/client/browserbugs/browserbugs.html
It talks about browsers misreading URLs like:
http://example.com/foo.pl?foo=bar®=foobar
Presuming this is within a HTML page e.g.:
http://example.com/foo.pl?foo=bar®=foobar";> ...
then the actual problem is
As I'm about to start working on the mp2 tutorials material, the mp2
online docs are going to be affected as well, since I usually sync the
two. I'd like to start including more practical examples of various
mod_perl handlers (HTTP handlers, but especially protocol and filters
ones).
For those using mod_perl2-RC3 or higher two new configuration options are
available: PerlPostConfigRequire and PerlConfigRequire
Apache 2 is not the same as Apache 1.3, so things are a bit different
under mp2 as well. I've updated the docs, so you can read about those
differences here:
Stas Bekman wrote:
allan juul wrote:
hello
we'd like the pages on perl.apache.org to print prettier while the
screen rendering should look as always, so we made a few changes that
hopefully didn't mess anything up.
we have only semi-tested this "feature" and would like a broader
browser/platfor
allan juul wrote:
hello
we'd like the pages on perl.apache.org to print prettier while the screen
rendering should look as always, so we made a few changes that hopefully didn't
mess anything up.
we have only semi-tested this "feature" and would like a broader
browser/platform matrix experience
hello
we'd like the pages on perl.apache.org to print prettier while the screen
rendering should look as always, so we made a few changes that hopefully didn't
mess anything up.
we have only semi-tested this "feature" and would like a broader
browser/platform matrix experience before commiting
hello
we'd like the pages on perl.apache.org to print prettier while the screen
rendering should look as always, so we made a few changes that hopefully didn't
mess anything up.
we have only semi-tested this "feature" and would like a broader
browser/platform matrix experience before commiting
ump anythings they want, and then we can merge some of those
> >>notes back into the docs.
> >
> >
> > Right then, unless someone comes up with something better:
> >
> > http://dahut.pm.org/mp_wiki
> >
> > I've been wanting to give so
Chris wrote:
On Wed, 09 Jun 2004 06:01:12 -0700, Stas Bekman wrote
Chris Shiflett wrote:
Alternatively, someone may want to start a wiki project where people
can dump anythings they want, and then we can merge some of those
notes back into the docs.
Right then, unless someone comes up with
On Wed, 09 Jun 2004 06:01:12 -0700, Stas Bekman wrote
> Chris Shiflett wrote:
>
> Alternatively, someone may want to start a wiki project where people
> can dump anythings they want, and then we can merge some of those
> notes back into the docs.
Right then, unless someon
Chris Shiflett wrote:
--- Stas Bekman <[EMAIL PROTECTED]> wrote:
2) docs need to have user comments.
I'm not sure it's a good idea. We already have a way too much
documentation. Instead of making it even harder for users to find
things, one should take the existing docs and impr
--- Stas Bekman <[EMAIL PROTECTED]> wrote:
> 2) docs need to have user comments.
>
> I'm not sure it's a good idea. We already have a way too much
> documentation. Instead of making it even harder for users to find
> things, one should take the existing docs and i
Stefan Loones wrote:
[...]
Then about the documentation:
[...]
Stefan and a few other folks have voiced a few concers about docs. I'll try to
address those here:
1) docs need to be improved and reorganized.
Well, docs need to be written. It's easy to suggest things, one needs to
actu
63 matches
Mail list logo
