Ports Search

POE component to create HTTP servers.

Run Maypole sub-requests as components

POE component to serve HTTP requests with a slightly different approach than POCo::Server::HTTP. Several useful built-in handlers for URIs not found, basic authentication, and parameter parsing.

PSGI Server implementation for POE.

This module makes serving SOAP/1.1 requests a breeze in POE.

This module makes serving up HTTP requests a breeze in POE.

POE::Filter::HTTP::Parser is a POE::Filter for HTTP which is based on HTTP::Parser. It can be used to easily create POE based HTTP servers or clients.

POEx::Role::PSGIServer encapsulates the core PSGI server behaviors into an easy to consume and extend role. It is based on previous POEx work such as POEx::Role::TCPServer which provides basic TCP socket multiplexing via POE::Wheel::SocketFactory and POE::Wheel::ReadWrite, and POEx::Role::SessionInstantiation which transforms plain Moose objects into POE sessions.

Parse::HTTP::UserAgent implements a rules-based parser and tries to identify MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla, Netscape, Robots and the rest will be tried with a generic parser. There is also a structure dumper, useful for debugging. User agent strings are a complete mess since there is no standard format for them. They can be in various formats and can include more or less information depending on the vendor's (or the user's) choice. Also, it is not dependable since it is some arbitrary identification string. Any user agent can fake another. So, why deal with such a useless mess? You may want to see the choice of your visitors and can get some reliable data (even if some are fake) and generate some nice charts out of them or just want to send an HttpOnly cookie if the user agent seems to support it (and send a normal one if this is not the case). However, browser sniffing for client-side coding is considered a bad habit.

Serializes and deserializes Path::Class objects as file:// URI.