Ports Search

The HTTP package supports client-side web programming in Haskell. It lets you set up HTTP connections, transmitting requests and processing the responses coming back, all from within the comforts of Haskell. It's dependent on the network package to operate, but other than that, the implementation is all written in Haskell. A basic API for issuing single HTTP requests + receiving responses is provided. On top of that, a session-level abstraction is also on offer (the BrowserAction monad); it taking care of handling the management of persistent connections, proxies, state (cookies) and authentication credentials required to handle multi-step interactions with a web server. The representation of the bytes flowing across is extensible via the use of a type class, letting you pick the representation of requests and responses that best fits your use. Some pre-packaged, common instances are provided for you (ByteString, String.)

Provides a simple means of reverse-proxying HTTP requests. The raw approach uses the same technique as leveraged by keter, whereas the WAI approach performs full request/response parsing via WAI and http-conduit.

The reCAPTCHA [1] is a service that provides captchas for preventing automated spam in web applications. The recaptcha-hs provides functions for using reCAPTCHA in Haskell web applications. [1] http://recaptcha.net/

Yesod is a framework designed to foster creation of RESTful web application that have strong compile-time guarantees of correctness. It also affords space efficient code and portability to many deployment backends, from CGI to stand-alone serving.

Drush is a command line shell and Unix scripting interface for the Drupal CMS and is designed to make life easier for those who spend some of their working hours hacking away at the command prompt.

The HttpCore components implement the most fundamental aspects of the HTTP protocol. They are nonetheless sufficient to develop basic client-side and server-side HTTP services with a minimal footprint and no external dependencies. The HttpCore base module contains the public API and the default implementation based on the Java classic (blocking) I/O model. It requires a Java 1.3 compatible runtime and has no dependency on any external libraries. HttpCore NIO extensions contain optional components that leverage the event driven, non-blocking I/O (NIO) model. HttpCore NIO extensions require a Java 5.0 compatible runtime and the HttpCore base module. HttpCore NIO extensions are intended for those usage scenarios where raw throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.

mod_asn is an Apache module that uses BGP routing data to look up the autonomous system (AS) and the network prefix (subnet) which contains a given (clients) IP address.

Apache module mod_limitipconn, which allows web server administrators to limit the number of simultaneous downloads permitted from a single IP address. Proxy tracking possibility is not supported yet since apache isn't patched.

mod_memcache_block is an Apache module that allows you to block access to your servers using a block list stored in memcache. It also offers distributed rate limiting based on HTTP response code.

This is a very small (7 Kb) HTTP server. It runs from inetd, which means its performance is poor. But for low-traffic sites, it's quite adequate. It implements all the basic features of an HTTP server.