the
SetHandler and add PerlHandler so it runs through mod_perl?
It doesn't work anymore...
(I added PerlSendHeader On, too)
Do you have any ScriptAlias statements in your conf file? Have you
tried changing from Options ExecCGI to Options +ExecCGI?
I think you should try to strip down the conf file
Perrin Harkins wrote:
Bleicke Holm wrote:
I continue to get returned the source-code. Searching the doc and
faqs
it looks as if I should turn on PerlSendHeader. But that's already done!
Make sure the file is executable by the user that the server is running
as.
I've checked that one
Bleicke Holm wrote:
Also, make sure that mod_perl is actually running by checking the
error_log as described in the docs.
For the time being there is no error message at all dans the error_log.
I was actually referring to this:
Bleicke Holm wrote:
I am quite desperately trying to get mod_perl working.
I continue to get returned the source-code. Searching the doc and faqs
it looks as if I should turn on PerlSendHeader. But that's already done!
Make sure the file is executable by the user that the server is running
Hi,
I am quite desperately trying to get mod_perl working.
I continue to get returned the source-code. Searching the doc and faqs
it looks as if I should turn on PerlSendHeader. But that's already done!
Also ExecCGI should be activated for the location.
In summary:
http://foot/cgi-bin/test.pl
into the right place.
If I call $r-send_http_header right after my $r-header_out(set_stuff)
directive, and then call $r-print(page contents), I get:
page_contents
HTTP_HEADERS DISPLAYED HERE (INCLUDING COOKIE HEADER)
Now, I experimented with PerlSendHeader being set to On, whilst disabling
the call to $r
I need mod_perl to not send the Content-type header when a program is
run. Despite the Off value of the PerlSendHeader variable in
httpd.conf, the header is still being sent.
This test program still sends an extraneous Content-type header:
print Content-type: text/html\n\n;
print h1Hello
Thanks, Tom. Yep, this does the job just fine and allows me to send
the Content-type later:
print HTTP/1.1 OK\n;
Is ignoring PerlSendHeader considered a feature? ;)
-gm
On Tue, 20 Nov 2001, Tom Mornini wrote:
This took me a LONG time to deal with when I was new to mod_perl...
Apache
shame on me, at some point I've commented out perlsendheader on :(
everything is fine...
sorry about that... must be a jetlag
On Sat, 31 Mar 2001, Stas Bekman wrote:
While verifying the correctness of the example in the book:
print "Content-type: text/plain\012\015\012\015"
the header from the script, the socket
persistence
worked with PerlSendHeader Off. So I guess I solved my problem although I don't
really
know why.
because CGI.pm will trigger a call to $r-send_http_header, regardless of
PerlSendHeader settings. whereas: "print Content-type: text/htm
On Mon, 2 Oct 2000, B. Burke wrote:
Why would the lack of a $r-send_http_header call cause socket persistence
to go away? I was under the impression that $r-send_http_header only affected
what was sent to the client, but appearantly it affects Apache's socket handling
as well.
because
On Thu, 28 Sep 2000, B. Burke wrote:
Once I changed how I was printing the header from the script, the socket
persistence
worked with PerlSendHeader Off. So I guess I solved my problem although I don't
really
know why.
because CGI.pm will trigger a call to $r-send_http_header, regardless
On Wed, 27 Sep 2000, B. Burke wrote:
When I set PerlSendHeader to Off in my perl.conf it doesn't send headers,
which
is good. The bad part is that it seems to break socket persistence for some
reason.
When I have PerlSendHeader set to On, I can open a socket with my test client
open and send receive
multiple
messages. When I set PerlSendHeader to Off, the socket closed after the 1st query.
I finally had success with socket persistence when I tried using CGI to print the
header
by replacing this:
print "Content-type: text/html\n\n";
with this:
print header(
When I set PerlSendHeader to Off in my perl.conf it doesn't send headers,
which
is good. The bad part is that it seems to break socket persistence for some
reason.
When I have PerlSendHeader set to On, I can open a socket with my test client,
and make multiple queries on the same socket.
Any
perlSendHeader On / Off -- what's the real difference?
i finally figured it out, after seeing many 'server errors'
on one hand, and http headers cluttering up the html output
to the browser on the other...
i have a perl script
test.npl
and a symbolic link to it
`ln -s test.npl
I've turned off PerlSendHeader, but no matter what I do, it seems that I'm
already getting headers before I ever print anything.
I have the following in my httpd.conf:
---(snip!)---
Alias /perl/ /home/httpd/perl/
Location /perl
SetHandler perl-script
PerlHandler Apache::Registry
"Benjamin Reed" [EMAIL PROTECTED] writes:
I've turned off PerlSendHeader, but no matter what I do, it seems that I'm
already getting headers before I ever print anything.
If you turn PerlSendHeader off, you are responsible for sending the
headers yourself. In the Apache API, and
18 matches
Mail list logo
