> On Wed, 14 Mar 2001, Perrin Harkins wrote:
>
> > On Wed, 14 Mar 2001, Issac Goldstand wrote:
> > > I still think that the above line is confusing: It is
> because mod_perl is
> > > not sending headers by itelf, but rather your script must provide the
> > > headers (to be returned by mod_perl)
Personally I'll admit that I've gotten screwed by this before... I usually
remember that it's a setting and set it one way, and then when my script
doesnt work, I set it the other way.
Of course I didnt read the docs thoroughly, but because it was confusing, I
just try it until it worked. Mayb
Hello,
SB>A small correction: "PerlSendHeader On makes mod_perl act just like
SB>mod_cgi with regard to HTTP headers" :)
+1 vote for adding this simple sentence, which IMO would clear up lots of
CGI to mod_perl beginner confusion.
Humbly,
Andrew
---
On Wed, 14 Mar 2001, Perrin Harkins wrote:
> On Wed, 14 Mar 2001, Issac Goldstand wrote:
> > I still think that the above line is confusing: It is because mod_perl is
> > not sending headers by itelf, but rather your script must provide the
> > headers (to be returned by mod_perl). However, w
rint:
7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Issac Goldstand" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 9:30 PM
Subject: Re: cgi_to_mod_perl m
On Wed, 14 Mar 2001, Issac Goldstand wrote:
> I still think that the above line is confusing: It is because mod_perl is
> not sending headers by itelf, but rather your script must provide the
> headers (to be returned by mod_perl). However, when you just say "mod_perl
> will send headers" it i
On Wed, 14 Mar 2001, Issac Goldstand wrote:
> So basically, PerlSendHeaders On means that it will send information such as
> the return code (eg HTTP/1.1 200 OK) ETag, Date and other headers that
> Apache generally handles on its own under mod_cgi?
>
> If so, then I think that all that really nee
- Original Message -
From: "Bill Moseley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 4:34 PM
Subject: Re: cgi_to_mod_perl manpage suggestion
> At 03:34 PM 03/14/01 +0200, Issac Goldstand wrote:
> >> On Tue, 13 Mar 2
At 03:34 PM 03/14/01 +0200, Issac Goldstand wrote:
>> On Tue, 13 Mar 2001, Andrew Ho wrote:
>> > PH>Um, you're getting me confused now, but PerlSendHeader On means that
>> > PH>mod_perl WILL send headers.
>
> I still think that the above line is confusing: It is because mod_perl is
>not sending
- Original Message -
From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Andrew Ho" <[EMAIL PROTECTED]>
Cc: "Issac Goldstand" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, March 14, 2001 4:56 AM
Subject: Re: cgi_to_mod_perl
On Tue, 13 Mar 2001, Andrew Ho wrote:
> PH>Um, you're getting me confused now, but PerlSendHeader On means that
> PH>mod_perl WILL send headers.
>
> I recognize this confusion. Most recovering CGI programmers think that
> "PerlSendHeader On" means that you no longer have to do this in your CGI:
>
Hello,
PH>Um, you're getting me confused now, but PerlSendHeader On means that
PH>mod_perl WILL send headers.
I recognize this confusion. Most recovering CGI programmers think that
"PerlSendHeader On" means that you no longer have to do this in your CGI:
print "Content-type: text/html\n\n";
On Tue, 13 Mar 2001, Issac Goldstand wrote:
> The only problem was the PerlSendHeaders option. The first fifty or
> so times that I read the manpages, I understood that PerlSendHeader On
> means that mod_perl will SEND HEADERS, and that off meant supply your
> own... Somehow I figured out (eventu
13 matches
Mail list logo
