After moving to mod_perl with Apache 2.2 I had this problem while running a
simple test.pl
The browser displayed: HTTP 500 - Internal Server Error and in the error.log
I could see malformed header from script and did not send an HTTP header
Several people helped me to navigate over multiple
Jeff Zhuk wrote:
...
Jeff,
whenever you send a message to the mod_perl list, I get a copy, because
I am subscribed to the list.
Then I get another copy, because you also send a copy to me directly.
So I get each message twice.
I guess it's the same for Randy.
It is not a real problem, but it is
On Dec 30, 2007 3:45 PM, Kate Yoak [EMAIL PROTECTED] wrote:
returning 200 as a scalar from a content handler causes Apache to
spit up Internal Server Error html despite a '200 OK' status.
There is no error or warning in the log, nor any other indication of
a problem
This is more of an apache
Apache to
spit up Internal Server Error html despite a '200 OK' status.
There is no error or warning in the log, nor any other indication of
a problem
sub handler{
return 200;
}
Generates the proper headers:
HTTP/1.1 200 OK
Date: Sun, 30 Dec 2007 03:12:03 GMT
Server: Apache/2.2.6
I am using mp2bug format for the message. Hope, that's ok!
=
-8-- Start Bug Report 8--
1. Problem Description:
I have just upgraded to apache2/modperl2 (bug report with specific
version info is below) and I am getting the
On 8/21/07, Jeff Pang [EMAIL PROTECTED] wrote:
PerlHandler Package::Name
instead of:
PerlHandler Package::Name-handler
So on the first case,we need to write the handler as
sub handler { my $r = shift; ...}
because Apache may call the function directly as Package::Name::handler.
on
On 8/21/07, Foo JH [EMAIL PROTECTED] wrote:
Are there any technical advantages with either method, or is it a
TIMTOWDI option given to the developers?
You can structure your code differently with method handlers, in ways
that appeal to some people. There's an example here:
2007/8/24, Perrin Harkins [EMAIL PROTECTED]:
On 8/21/07, Jeff Pang [EMAIL PROTECTED] wrote:
PerlHandler Package::Name
instead of:
PerlHandler Package::Name-handler
So on the first case,we need to write the handler as
sub handler { my $r = shift; ...}
because Apache may call
On 8/23/07, Foo JH [EMAIL PROTECTED] wrote:
I've read http://perldoc.perl.org/attributes.html about attributes, but
it does not seem to suggest that tagging the method attribute to
subroutine has any programming advantages, unless you're interested to
list the subroutines with that attribute.
Hello Perrin,
I'm interested in how you defined your handler with the 'method' attribute:
sub handler : method {
...
I've read http://perldoc.perl.org/attributes.html about attributes, but
it does not seem to suggest that tagging the method attribute to
subroutine has any programming
On 8/23/07, Jeff Pang [EMAIL PROTECTED] wrote:
why it need prototype in mp1's method handler?
Subroutine attributes did not exist before perl 5.6.
- Perrin
Hello,
I have a module that will fail every once in a while with the error_log
message:
Can't call method send_http_header on an undefined value at
/path/to/module/Name.pm
The handler method starts out with:
sub handler ($$) {
my ($class, $r) = @_;
For some reason $r is not defined.
Try change the codes to:sub handler { my $r = shift; ...-Original Message-
From: Jordan McLain <[EMAIL PROTECTED]>
Sent: Aug 22, 2007 9:26 AM
To: mod_perl <modperl@perl.apache.org>
Subject: Internal Server Error
Hello,I have a module that will fail every once in a while with t
On 8/21/07, Jordan McLain [EMAIL PROTECTED] wrote:
sub handler ($$) {
my ($class, $r) = @_;
For some reason $r is not defined. This only happens intermittently... Does
anyone have any ideas?
Sounds like sometimes it doesn't get properly called as a method, so
$r ends up as the first
Jeff Pang wrote:
Try change the codes to:
sub handler {
my $r = shift;
...
If his handler is called as a method, $class is an appropriate first
variable to shift out of @_. Using ($class, $r) = @_ is a perfectly
legitimate way of taking care of that.
Colin
McLain [mailto:[EMAIL PROTECTED]
*发送时间:* 2007年8月22日 9:26
*收件人:* mod_perl
*主题:* Internal Server Error
Hello,
I have a module that will fail every once in a while with the error_log
message:
Can't call method send_http_header on an undefined value at
/path/to/module/Name.pm
The handler
I might have solved my own problem...
I was calling:
PerlHandler Package::Name
instead of:
PerlHandler Package::Name-handler
although I am still confused as to why the first was working...
Jordan
On 8/21/07, Colin Wetherbee [EMAIL PROTECTED] wrote:
Jeff Pang wrote:
Try change the codes
-Original Message-
From: Jordan McLain [EMAIL PROTECTED]
Sent: Aug 22, 2007 10:52 AM
To: modperl@perl.apache.org
Subject: Re: Internal Server Error
I might have solved my own problem...
I was calling:
PerlHandler Package::Name
instead of:
PerlHandler Package::Name-handler
So
hai,
I have encountered an error when i access the homepage. if possible give
me the solution to resolve this problem . Thank You
*The error is *
**
An internal server error occurred on http://localhost:8080/xdams:
Date: 3/5/07 6:23 PM
Session ID: 0FA0F70BB560560A23B187A54718A5CD
-- URL
On Monday 05 March 2007 08:20, Viji ayyanar wrote:
hai,
I have encountered an error when i access the homepage. if possible give
me the solution to resolve this problem . Thank You
*The error is *
**
An internal server error occurred on http://localhost:8080/xdams:
Date: 3/5/07 6:23 PM
Hi,
I am trying to run a simple Perl CGI script and I get the following error..Can anyone help me on this
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [EMAIL PROTECTED
Check your Apache error logs. "More information about this error
may be available in the server error log."
From: Deepak Mallya
[mailto:[EMAIL PROTECTED] Sent: Monday, August 21, 2006 4:42
PMTo: modperl@perl.apache.orgSubject: Getting internal
server error when I ru
Deepak Mallya wrote:
Hi,
I am trying to run a simple Perl CGI script and I get the following
error..Can anyone help me on this
This isn't really a mod_perl question, but I'm betting its because you need to
do
chmod 755 file
or similiar.
Also, make sure that /usr/bin/perl is a valid
On Mon, 21 Aug 2006, Deepak Mallya wrote:
Hi,
I am trying to run a simple Perl CGI script and I get the following
error..Can anyone help me on this
As others have noted, this isn't a mod_perl problem.
Help running cgi scripts is available at
On Tuesday 30 August 2005 08:12 am, Mahesh kumar wrote:
Please reply to the list, not directly to me. Thanks.
Apache/2.0.54 (Unix) mod_perl/1.99_16 Perl/v5.8.7 Server at
sssupport.asad.srishti Port 80
[Tue Aug 30
Stas Bekman wrote:
Arshavir Grigorian wrote:
Hello list,
I just tried searching for 'path_info' in the 2.0 docs and got an
internal server error(500).
http://perl.apache.org/search/swish.cgi?query=path_infosbm=SecIsubmit=search
The /x1/log/www/error_log says:
[Wed Nov 17 15:01:50 2004] [error
Hello list,
I just tried searching for 'path_info' in the 2.0 docs and got an
internal server error(500).
http://perl.apache.org/search/swish.cgi?query=path_infosbm=SecIsubmit=search
Hope it's easy to fix.
Best, Arshavir
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http
Thanks for your response. However at the moment what I needed was perl to work
on my webserver for testing purpose only on a global level. I found a way to
enable perl using an apache directive and bypassed mod_perl altogether. So for
the time being everything is fine. Thanks for you
AddHandler cgi-script .cgi .pl to the configuration. Now
when I try to run any perl script or cgi script I get an internal server error
500. With some vauge stuff in the error log that dosn't seem to be pertant at
all. Ceratinaly not a cause for an internal error. Its not like the world
would
ExecCGI to the options, then added AddHandler
cgi-script .cgi .pl to the configuration. Now when I try
to run any perl script or cgi script I get an internal
server error 500. With some vauge stuff in the error log
that dosn't seem to be pertant at all. Ceratinaly not a
cause for an internal
tks for the direction. i uninstalled apache-asp. went into site\lib\ppm.xml
and adjusted the record so that uwinnipeg is the first repository.
installed with ppm. did a query to verify. went to the apache\asp.pm to
verify manually.
tried the system. and no failure messages after 30 screens.
so
in brief, i am trying to find where modperl generates the infamous OK: The
server encountered an internal error
hopefully there is a decent way to either drop the error message, or at the
least turn it into something that does not jar the client trying to use my
system.
i wrote a rather
john z wrote:
in brief, i am trying to find where modperl generates the infamous OK:
The server encountered an internal error
hopefully there is a decent way to either drop the error message, or at
the least turn it into something that does not jar the client trying to
use my system.
i
33 matches
Mail list logo
