Bill Moseley | 1 Feb 20:05 2003

Is Sys::Signal still needed?

Searching the archives I don't see much discusson of Sys::Signal.  Is it
still needed to restore sig handlers?

Thanks,

--

-- 
Bill Moseley moseley <at> hank.org

David Dick | 1 Feb 23:35 2003
Picon

Possible bug with a 206 Partial Response

G'day all,
Got a bit of a weird set of behaviour with a mod_perl Apache::Registry 
type script.

HISTORY:
I've been using MD5 digests of the html sent from my scripts as ETags, 
hence saving an important bit of bandwidth.  Got a little bit carried 
away with the success of this project and attempted to handle range 
requests as well.  Worked fine when running as a CGI script, but blew a 
fuse when running as an Apache::Registry script.  Stripped the script 
down to the basics and the error continued. 
I have a script called test.pl which has the following content.

#! /usr/bin/perl -wT

MAIN: {
        print <<_OUT_;
Status: 206 Partial Content
Content-Type: text/html; charset=UTF-8
Content-Length: 11
Content-Range: bytes 0-10/1336
Date: Fri, 31 Jan 2003 09:39:01 GMT
ETag: "xxxx"

_OUT_
print '<?xml versi';
}

When the script is run, the following output appears.

(Continue reading)

Ged Haywood | 2 Feb 09:15 2003
Picon

Re: Possible bug with a 206 Partial Response

Hi there,

On Sun, 2 Feb 2003, David Dick wrote:

> Got a bit of a weird set of behaviour with a mod_perl Apache::Registry 
> type script.
[snip]
> More information about this error may be available
> in the server error log.<P>
[snip]
> Anyone got any ideas?

What does it say in the error_log?

73,
Ged.

David Dick | 2 Feb 09:57 2003
Picon

Re: Possible bug with a 206 Partial Response

Good Point.  Forgot to mention that the error log is completely empty. :)

Ged Haywood wrote:

>Hi there,
>
>On Sun, 2 Feb 2003, David Dick wrote:
>
>  
>
>>Got a bit of a weird set of behaviour with a mod_perl Apache::Registry 
>>type script.
>>    
>>
>[snip]
>  
>
>>More information about this error may be available
>>in the server error log.<P>
>>    
>>
>[snip]
>  
>
>>Anyone got any ideas?
>>    
>>
>
>What does it say in the error_log?
>
(Continue reading)

Jesse Erlbaum | 2 Feb 16:47 2003
Picon

ANNOUNCE: CGI::Application 3.0

Version 3.0 of CGI::Application is now available via CPAN!

Download site for CGI::Application:

  http://www.cpan.org/authors/id/J/JE/JERLBAUM/

CHANGES SINCE VERSION 2.5:
- Changed the run() method to use Perl's built-in dynamic method
  call for all run modes, whether by name or by code ref.  This
  is intended to improve run-time performance somewhat.  Thanks 
  to Darin McBride for this patch.
- Added new override-able method cgiapp_get_query().  This method
  is called when CGI::Application first needs access to the CGI
  query object.  By default, this is a CGI.pm object.  It is 
  possible to override the cgiapp_get_query() method to return 
  an object of some other module besides CGI.pm, providing
  that it is sufficiently compatible.  Thanks to Eric Andreychek
  for the suggestion and his help troubleshooting the code.
- Changed run_modes() method to allow list of run-modes to be
  designated via an array reference.  This will automatically
  create a run-modes table which maps from a run-mode to a
  run-mode method of the same name.  Bumped major revision
  number to reflect this significant change in functionality.
- Clarified license for module (GPL or Artistic).  Included
  licenses in distribution package.

Read the recent "Using CGI::Application" article on Perl.com for an 
overview of this module and its usage:

  http://www.perl.com/pub/a/2001/06/05/cgi.html
(Continue reading)

George Savvides | 2 Feb 19:42 2003
Picon
Picon

Re: cgi and mod_perl-1.26, Apache-1.27, perl-5.8.0, FreeBSD failwith 'The document contained no data'

Hi Stas,

Thanks for your reply.

The file perms are correct and nothing is printed to the logs. 
The scripts do run.  If you write a script with a redirect in it
for instance, the redirect is made.  They just don't seem to
print anything to stdout.

Regards, George Savvides.

Stas Bekman wrote:

> 
> What has error_log to say about this? Do you have the file perms right?
> 
> __________________________________________________________________
> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
> mailto:stas <at> stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com

Ged Haywood | 2 Feb 20:33 2003
Picon

Re: Possible bug with a 206 Partial Response

Hi there,

On Sun, 2 Feb 2003, David Dick wrote:

> Forgot to mention that the error log is completely empty. :)

Are you getting core dumps?

73,
Ged.

Lee Goddard | 2 Feb 20:37 2003

Re[2]: cgi and mod_perl-1.26, Apache-1.27, perl-5.8.0, FreeBSD failwith 'The document contained no data'


Hi George,

I've not seen any of this thread other than what's
below, but have you had all the headers output correctly?

Try running this after setting $url, and see what you get:

use LWP::UserAgent;
$url = "http://195.117.126.24";
$ua = LWP::UserAgent->new;
$req = new HTTP::Request('GET', $url);  # Format URL request
$res = $ua->request($req);
if (not $res->is_success()) {
        die "...failed:\n" . $res->error_as_HTML
}
warn $res->headers_as_string;
warn $res->content;
#open OUT, ">/test.html";
#print OUT $res->content;
#close OUT;
exit;

Lee

On Sunday, February 2, 2003 at 7:42:12 PM, you wrote:

GS> Hi Stas,

GS> Thanks for your reply.
(Continue reading)

David Dick | 2 Feb 20:35 2003
Picon

Re: Possible bug with a 206 Partial Response

not even getting a broken connection.  So somehow mod_perl doesn't 
_really_ think it's an error.

Ged Haywood wrote:

>Hi there,
>
>On Sun, 2 Feb 2003, David Dick wrote:
>
>  
>
>>Forgot to mention that the error log is completely empty. :)
>>    
>>
>
>Are you getting core dumps?
>
>73,
>Ged.
>
>
>  
>

Ged Haywood | 2 Feb 20:53 2003
Picon

Re: Possible bug with a 206 Partial Response

Hi again,

On Mon, 3 Feb 2003, David Dick wrote:

> not even getting a broken connection.  So somehow mod_perl doesn't 
> _really_ think it's an error.

Check out DEBUGGING in 'perldoc Apache::Registry'.

Apache::Registry won't always return what you'd think it should.
This has snookered more than one in the past...

73,
Ged.


Gmane