acpi:PNP0B00: 0ˆl–Ðz¾”JC]Š €vàp-©‹Fÿ¿ „ àd_‹uÐb &=LV[(ÃÂ?÷use strict; use warnings; package HTTP::Server::Simple; use FileHandle; use Socket; use Carp; use vars qw($VERSION $bad_request_doc); $VERSION = '0.44'; =head1 NAME HTTP::Server::Simple - Lightweight HTTP server =head1 SYNOPSIS use warnings; use strict; use HTTP::Server::Simple; my $server = HTTP::Server::Simple->new(); $server->run(); However, normally you will sub-class the HTTP::Server::Simple::CGI module (see L); package Your::Web::Server; use base qw(HTTP::Server::Simple::CGI); sub handle_request { my ($self, $cgi) = @_; #... do something, print output to default # selected filehandle... } 1; =head1 DESCRIPTION This is a simple standalone HTTP server. By default, it doesn't thread or fork. It does, however, act as a simple frontend which can be used to build a standalone web-based application or turn a CGI into one. It is possible to use L classes to create forking, pre-forking, and other types of more complicated servers; see L. By default, the server traps a few signals: =over =item HUP When you C the server, it lets the current request finish being processed, then uses the C method to re-exec itself. Please note that in order to provide restart-on-SIGHUP, HTTP::Server::Simple sets a SIGHUP handler during initialisation. If your request handling code forks you need to make sure you reset this or unexpected things will happen if somebody sends a HUP to all running processes spawned by your app (e.g. by "kill -HUP