Ports 搜索

HTTP::Server::Simple::Authen is an HTTP::Server::Simple plugin to allow HTTP authentication. Authentication scheme is pluggable and you can use whatever Authentication protocol that Authen::Simple supports. You can use authenticate method whatever you want to authenticate the request. The method returns $username taken from the request if the authentication is successful, and undef otherwise. The code in "SYNOPSIS" requires authentication for all the requests and behaves just the same as Apache's Require valid-user.

An abstract baseclass for a standalone mason server.

HTTP::Server::Simple::PSGI is a HTTP::Server::Simple based HTTP server that can run PSGI applications. This module only depends on HTTP::Server::Simple, which itself doesn't depend on any non-core modules so it's best to be used as an embedded web server.

This module allows you to record all HTTP communication between an HTTP::Server::Simple-derived server and its clients. It is a mixin, so it doesn't itself subclass HTTP::Server::Simple; you need to subclass from both HTTP::Server::Simple::Recorder and an actual HTTP::Server::Simple subclass, and HTTP::Server::Simple::Recorder should be listed first.

HTTP::Server::Simple is a very simple standalone HTTP daemon with no non-core module dependencies. It's ideal for building a standalone http-based UI to your existing tools.

Maintain session IDs using mobile phone's unique id.

Store session data in DBI for HTTP::Session.

Yet another session manager. Easy to integrate with HTTP::Engine.

HTTP::Session2 is yet another HTTP session data management library.

You don't have to know anything about objected-oriented Perl, LWP, or the HTTP module to be able to check your links. This module is designed for the casual user. It has one function, check_link, that returns the HTTP response code that it receives when it tries to fetch the web address passed to it. The undef value is returned for any non-HTTP failure and the $HTTP::SimpleLinkChecker::ERROR variable is set. The HEAD method is tried first, although if anything other than a good status code (those less than 400) is received, another request is made with the GET method. Note, however, that even with the best code, no module can control how servers decide to respond to a check, or control any of the myriad things that can go wrong with the network between you and the remote server. Some may filter requests based on origin IP address, user-agent type, or any other arbitrary factor. Some servers may not respond correctly at all. Furthermore, some servers might be temporarily down or overloaded. I recommend that you recheck "broken" links a couple times over a long period (like a day or two) before you decide they are really broken.