]>
Commit | Line | Data |
---|---|---|
4caa34ae | 1 | Source: libhttp-daemon-perl |
e4857125 | 2 | Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org> |
4caa34ae | 3 | Section: perl |
aa890074 | 4 | Testsuite: autopkgtest-pkg-perl |
4caa34ae | 5 | Priority: optional |
0812229c | 6 | Build-Depends: debhelper (>= 10) |
300288fa | 7 | Build-Depends-Indep: perl, |
e4857125 | 8 | libhttp-date-perl, |
9 | libhttp-message-perl, | |
10 | libio-socket-ip-perl, | |
11 | liblwp-mediatypes-perl | |
143cb5c9 | 12 | Standards-Version: 4.3.0 |
081adbe9 | 13 | Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libhttp-daemon-perl |
e4857125 | 14 | Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libhttp-daemon-perl.git |
15 | Homepage: https://metacpan.org/release/HTTP-Daemon | |
4caa34ae NB |
16 | |
17 | Package: libhttp-daemon-perl | |
18 | Architecture: all | |
e4857125 | 19 | Depends: ${misc:Depends}, |
20 | ${perl:Depends}, | |
21 | libhttp-date-perl, | |
22 | libhttp-message-perl, | |
23 | libio-socket-ip-perl, | |
24 | liblwp-mediatypes-perl | |
4caa34ae | 25 | Breaks: libwww-perl (<< 6.00) |
e4857125 | 26 | Replaces: libwww-perl (<< 6.00) |
4caa34ae NB |
27 | Description: simple http server class |
28 | Instances of the HTTP::Daemon class are HTTP/1.1 servers that listen on a | |
29 | socket for incoming requests. The HTTP::Daemon is a subclass of | |
30 | IO::Socket::INET, so you can perform socket operations directly on it too. | |
31 | . | |
32 | The accept() method will return when a connection from a client is available. | |
33 | The returned value will be an HTTP::Daemon::ClientConn object which is | |
34 | another IO::Socket::INET subclass. Calling the get_request() method on this | |
35 | object will read data from the client and return an HTTP::Request object. The | |
36 | ClientConn object also provide methods to send back various responses. | |
37 | . | |
38 | This HTTP daemon does not fork(2) for you. Your application, i.e. the user of | |
39 | the HTTP::Daemon is responsible for forking if that is desirable. Also note | |
40 | that the user is responsible for generating responses that conform to the | |
41 | HTTP/1.1 protocol. |