Ports Search

PHProxy is a web HTTP (for now; FTP is not supprted yet) proxy programmed in PHP designed to bypass firewalls and other proxy restrictions through a web interface very similar to the popular CGIProxy. The server that this script runs on simply acts as a medium that retrives resources for you. The only IP address shown will be the server's IP address. So basically, it is indirect browsing. The only catch being that the server has to has access to those otherwise inaccessible resources.

Pligg is an Open Source Web 2.0 CMS. The main features that make Pligg unique are collaborative bookmarking, social networking, folksonomy and blogging. Each of the News links, unit of pligg content, has a vote button, URL and optionally a short description of news. Here Visitors are supplier, consumer and judge of the content. Every visitor has right and freedom to vote and veto any news item. At the end of the day, depending on count of vote news are either promoted to main site,or move or remains in incoming queue, or permanently removed from site. Being a collaborative CMS, Pligg sites grow very fast in terms of traffic and popularity.

mod_fileiri implements http IRIs for directories/files, i.e. if accepts URIs with non-ASCII characters encoded in UTF-8 and converts them to the legacy encoding used in the file system (which can be specified per directory, or even finer if necessary (although that's a real hack)). What is more, it continues to accept requests in the legacy encoding specified, and redirects them to the correct UTF-8 form, which then returns the actual document (without looping). There is also a backwards mode, which does redirects from URIs in a specified legacy encoding to UTF-8 if the directory/ filenames are in UTF-8.

This plugin implements the Catalyst::Authentication v.10 API. This plugin uses Net::LDAP to let your application authenticate against an LDAP directory. It has a pretty high degree of flexibility, given the wide variation of LDAP directories and schemas from one system to another. It authenticates users in two steps: 1) A search of the directory is performed, looking for a user object that matches the username you pass. This is done with the bind credentials supplied in the "binddn" and "bindpw" configuration options. 2) If that object is found, we then re-bind to the directory as that object. Assuming this is successful, the user is Authenticated.

Catalyst::Enzyme is a layer on top of the Catalyst framework providing CRUD functionality for Class::DBI models. Enzyme uses convention and configuration to provide e.g. extensible CRUD out-of-the-box, and a common way of dealing with error handling etc. It's not completely unlike Maypole in this regard. However, at this point Enzyme isn't as feature-rich as Maypole. Enzyme is one way of bringing many Catalyst modules and concepts together into a unified whole. There are other ways to do this (obviously. This is, like... uh, Perl).

If your Catalyst project logs many messages, logging via standard error to Apache's error log is not very clean: The log messages are mixed with other web applications' noise; and especially if you use mod_fastcgi, every line will be prepended with a long prefix. An alternative is logging to a file. But then you have to make sure that multiple processes won't corrupt the log file. The module Log::Handler by Jonny Schulz does exactly this, because it supports message-wise flocking. This module is a wrapper for said Log::Handler.

This is a collection of modules that represent, create, and extract information from HTML syntax trees. The modules present in this collection are: HTML::Element - represents the nodes of the HTML syntax trees. The elements have other elements and text segments as children. The HTML::Element class have methods to methods to build, alter, and traverse the structure of the tree. HTML::TreeBuilder - uses HTML::Parser to read HTML document text and build from it a syntax tree made of HTML::Element nodes. HTML::Parse - deprecated. Now just a wrapper around HTML::TreeBuilder HTML::AsSubs - Easy way to build an HTML syntax tree by nesting functions.

Although using the conventional LWP::UserAgent is fast and easy it does have some drawbacks - the code execution blocks until the request has been completed and it is only possible to process one request at a time. HTTP::Async attempts to address these limitations. It gives you a 'Async' object that you can add requests to, and then get the requests off as they finish. The actual sending and receiving of the requests is abstracted. As soon as you add a request it is transmitted, if there are too many requests in progress at the moment they are queued. There is no concept of starting or stopping - it runs continuously.

Mason is a powerful Perl-based templating system, designed to generate dynamic content of all kinds. Unlike many templating systems, Mason does not attempt to invent an alternate, "easier" syntax for templates. It provides a set of syntax and features specific to template creation, but underneath it is still clearly and proudly recognizable as Perl. Mason is most often used for generating web pages. It has a companion web framework, Poet, designed to take maximum advantage of its routing and content generation features. It can also be used as the templating layer for web frameworks such as Catalyst and Dancer.

This module provides a interface between HTML::Mason and Apache::Session, in effect, providing full session and cooking handling from within HTML::Mason. When run under the ApacheHandler module, this module attempts to first use Apache::Cookie for cookie-handling. Otherwise it uses CGI::Cookie as a fallback. This module accepts quite a number of parameters, most of which are simply passed through to Apache::Session. For this reason, you are advised to familiarize yourself with the Apache::Session documentation before attempting to configure this module. Use 'perldoc MasonX::Request::WithApacheSession' for information on how to use the module. MasonX::Request::WithApacheSession was written by Dave Rolsky.