Hi there,
On 1 Nov 2002, Clinton Gormley wrote:
I'm struggling to get anything much working with mod_perl 2.
[snip]
I have read all of the documentation on perl.apache.org.
Are you sure? :)
If these things should be working,
Well it does say on the home page that it's the Bleeding Edge.
Clinton Gormley wrote:
I'm struggling to get anything much working with mod_perl 2.
I have installed mod_perl 1.99_07 with Apache 2.0.43. I have read all of
the documentation on perl.apache.org.
I can get a basic page returned to me with a modperl handler, but as
soon as I try to do anything
Hi,
well I have read all (whatever scanty little
available) docs on mod_perl 2 and am pretty
disappointed.
For example Apache::Request is not ready yet so you
need Apache::compat and mod_perl 1 for basic POST
request handling and parsing.
In my opinion, stay with mod_perl 1.
-Sumitro Chowdhury.
On Fri, 1 Nov 2002, Sumitro Chowdhury wrote:
Hi,
well I have read all (whatever scanty little
available) docs on mod_perl 2 and am pretty
disappointed.
Additions, I'm sure, are welcome :)
For example Apache::Request is not ready yet so you
need Apache::compat and mod_perl 1 for basic POST
--- Randy Kobes [EMAIL PROTECTED] wrote:
On Fri, 1 Nov 2002, Sumitro Chowdhury wrote:
Hi,
well I have read all (whatever scanty little
available) docs on mod_perl 2 and am pretty
disappointed.
Additions, I'm sure, are welcome :)
For example Apache::Request is not ready yet so
On Fri, 1 Nov 2002, Sumitro Chowdhury wrote:
H
I thought POST request handling needs
$r-read($buf,$r-headers_in-{'Content-length'})
and GET request handling needs
$r-args();
Sorry about that - I should have read more carefully that
you were specifically referring to POSTed data -
--- Randy Kobes [EMAIL PROTECTED] wrote:
my %args = $r-Apache::args;
is for GET requests. For POST, as is described in
the
content() method of Apache::compat, for now one can
use
$r-setup_client_block;
# return an error unless $r-should_client_block;
my $len =
