Hi,
I don't think this changes your situation any. CGI is not really fast
enough to use, so you still need mod_perl or FastCGI. Because the
current crop of linux distros came out before mod_perl 2 but couldn't
use mod_perl 1 (since they are using apache 2), they have poor mod_perl
support in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Justin,
I try to answer you questions step by step:
1. Why does print "Content-type: text/html\r\n\r\n" work?
Because $r->content_type("text/html") does the same behind the scences
2. Should I use Apache2::RequestUtil->request():
This is only ava
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Schaefer wrote:
> Boysenberry Payne <[EMAIL PROTECTED]> writes:
>
>
>>What is the difference between:
>>
>>APR::Request::Apache2
>>and
>>Apache2::RequestRec
>
>
> Apache2::RequestRec is the perl module representing httpd's request_rec
> struct.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Boysenberry Payne wrote:
> Now when I try to start apache using apachectl start I get:
>
> dyld: /usr/local/httpd/bin/httpd version mismatch for library:
> /usr/local/httpd/lib/libexpat.0.dylib (compatibility version of user:
> 6.0.0 greater than libr
Jonathan Steffan wrote:
1.
Concept:
2.
3.
GET http://domain.tld/search/a/b/c (via :80)
4.
rewrite search/a/b/c ->
http://localhost:8080/perl/script?a=a&b=b&c=c [P] (via .htaccess
RewriteRule) [OK] (localhost:8080 is another apache w/mod_perl)
5.
proxy
Thanks for your reply.
But why get into all of this confusion when:
print "Content-type: text/html\r\n\r\n"
just works?
Why would I want to use:
$request = Apache2::RequestUtil->request();
-Original Message-
From: Tom Schindl [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 15,
On Wed, 2005-09-14 at 18:07 -0700, David Christensen wrote:
> and tentatively plan to use the Debian 3.1 stable apache-perl package (Apache
> 1.33 and mod_perl 1.29).
That sounds like a good plan. There may still be issues with their
apache compile, but it's definitely better than using a pre-rel
I'd like to do the following:
open $fh, '<', 'some_file'; # A very big file
$b = APR::Bucket->new($ba, $fh);
while($b->read($buffer, 2048)) {
...
}
or
$b = APR::Bucket->new($ba, \*STDIN);
On Fri, Sep 16, 2005 at 12:25:24AM +0300, Nikolay Ananiev wrote:
>
>
> I'd like to do the following:
> open $fh, '<', 'some_file'; # A very big file
> $b = APR::Bucket->new($ba, $fh);
>
> while($b->read($buffer, 2048)) {
> .
> }
>
> or
> $b = APR::Bucket->new($ba, \*STDIN);
>
>
>
>
>
On Fri, 16 Sep 2005 00:25:24 +0300
"Nikolay Ananiev" <[EMAIL PROTECTED]> wrote:
> I'd like to do the following:
> open $fh, '<', 'some_file'; # A very big file
> $b = APR::Bucket->new($ba, $fh);
>
> while($b->read($buffer, 2048)) {
> ...
> }
>
> or
> $b = APR::Bucket->new($ba, \*STDIN);
Why
hi,
On Tue, 30 Aug 2005, Octavian Rasnita wrote:
> Does anyone use the templating system HTML::Template::Compiled with
> mod_perl?
>
> I have just discovered that it works much faster with mod_perl than
> HTML::Template and I have also seen that it has some new features but I
> wouldn't like to
Hello
I'm using Apache2 and ModPerl2 on Fedora Core 4 x86_64 and I discover some
problem when client try to get nonexistent script uri
(http://my.site.com/foo.pl).
Client doesn't obtain any response or error page.
Petr Dadak
Univesity IS development at Mendel university Brno, Czech Republic
Greetings. I've been scouring the list and the net for a solution for
this but my apologies in advance if I didn't get the search terms right
and missed a RTFM answer.
I work for a web hosting company and we recently purchased a pair of
BigIPs. These have the ability to terminate SSL connections a
Hi Mark,
From my limited knowledge, SSL handshake is processed prior doing the HTTP
request-response. Therefore, when apache or mod_perl accepts HTTPS requests,
it can't redirect it over HTTPS unless you create another HTTPS request with
LWP or WWW::Mechanize, for example.
But if you want to
Howdy. Actually, I don't need any actual SSL functionality. All I need
to do is to trick everything from the transhandler phase downwards that
the URL's scheme is 'https' so that redirects have https://, not
http://, since anyone doing a mod_rewrite or scripted redirect whilst
in SSL would get shun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Moseley wrote:
> Howdy. Actually, I don't need any actual SSL functionality. All I need
> to do is to trick everything from the transhandler phase downwards that
> the URL's scheme is 'https' so that redirects have https://, not
> http://, since a
16 matches
Mail list logo
