Free http server simple recorder 0.02 software for linux

GTP server simulator is a simple responder for the GTP (GTP prime) protocol that works with the Cisco Content Services Gateway to provide per-user traffic limits.

GTP` (GTP prime) server simulator (it permits any content and provide quadrants for every operation) binaries for Linux (run under Fedora Core 4 and 5).

The binary was tested with Cisco CSG.

httptype is a program that returns the http host software of a website. It is written in Perl.
httptype reads a list of http hosts and optionally the port number for each of these. It queries each host, displaying the type of HTTP server running on that host. It reads the http_proxy and no_proxy environment variables to determine whether to use a proxy or not.
httptype reads a list of http servers and, optionally, the port number for each of these. It then queries each of the hosts and displays the HTTP server software of the host.
Input may be read from a host file if specified using the --hosts switch:
httptype --hosts [hostfile]
If hostfile is omitted or `-, httptype reads from standard input. See Format of host file for more info.
A single host may be queried by passing its name on the command line:
httptype host [port]
If port is omitted, 80 is used.
If no host file is specified through the --hosts file and no host is specified on the command line, httptype will read the list from standard input. See Format of host file for more info.
httptype will read the http_proxy environment variable and try to determine if a proxy server is being used. This setting may be overridden using the --proxy switch:
httptype --proxy proxyhost[:proxyport]
If proxyport is omitted, 80 is used.
If the proxy server is `none, no proxy is used. This is typically used to prevent httptype from using the proxy server specified by http_proxy. The --noproxy switch can be used to achieve the same.
Additionally, you may use the no_proxy environment variable to specify a comma delimited list of hosts for which httptype should not use the proxy. If httptype comes across any of these hosts, it will make a direct connection to them.
Enhancements:
- made 1.3.8 stable and renamed to 1.2.3

The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows NT. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards.
Apache has been the most popular web server on the Internet since April of 1996. The May 2003 Netcraft Web Server Survey found that 62% of the web sites on the Internet are using Apache, thus making it more widely used than all other web servers combined.
The Apache HTTP Server is a project of the Apache Software Foundation.

mod_perlservice enables you to directly call perl methods and get return value over the internet.

mod_perlservice? What is that?

The cool new way to do remoting with Perl and Apache! But, lets start by breaking that crazy name apart. mod - perl - service

mod - Its a module for the popular and ubiquitous Apache HTTP Server.
perl - Of course, its the popular and ubiquitous programming language.
service - Ah, this is the unique part. Its the new ingredient that unifies Apache, Perl and XML into an easy to use web-services system.

With the mod_perlservice system, you can write perl subs and packages on your server and call them over the internet from client code. Clients can pass scalars, arrays and hashes to the server-side subroutines and obtain the return value ( scalar, array or hash ) back from the remote code. Some folks refer to this functionality as "remoting" or "RPC", so if you like, you can say mod_perlservice is remoting with Perl and Apache. Client programs may be written in a variety of languages; libraries for C, Perl, and Flash Action Script are all ready to go!

Now that you know what mod_perlservice is, lets look at why it is. The author (Thats me!) believes that mod_perlservice has a very clean, easy-to-use interface when compared with other RPC systems. Also, since it builds on the Apache platform, it benefits from Apaches ubiquity, security, and status as a standard. Since mod_perlservice sports an embedded perl interpreter, it offers high performance for demanding applications.

So what can I use this mod_perlservice for?

You can use it to create networked applications that require client-server communication, information processing and sharing. mod_perlservice is for applications and you will not use it to create dynamic content for your HTML pages. However, you surely can use it for Flash remoting with Perl.

Here are some usage examples:

A desktop application (written using your favorite C++ GUI library) that records the current local air temperatue and sends it to an online database every 10 minutes. The server can be queried to obtain the current and historical local air temperature of any other participating client.

A Flash-based stock portfolio management system. You can create model stock portfolios and retrieve realtime stock quote information and news.

A command-line utility in Perl that accepts English sentences on standard input and outputs the sentences in French. Translation occurs in server-side Perl code. If the sentence is idomatic and the translation is incorrect, the user has the option of sending the server a correct translation that will be stored in an online idiom database.

Dwarf HTTP Server is a full-featured and ready-to-use web server with the Java Servlet API 2.2 and Java Server Pages 1.1 implementation.
Dwarf HTTP Server can be used either standalone or embed in a larger hosting application, free of charge for the binary redistribution
Since the server is based on the Dwarf framework, it shares its common design principles and features - simplicity, high modularity and extensibility, authentication and authorization, XML-based configuration, logging and remote management.
Main features:
- multi-threaded design
- dynamically adjusted number of active threads
- Java Servlet API 2.2 implementation
- Java Server Pages 1.1 (by Apache Tomcat/Jasper)
- HTTP/1.1 and CGI/1.1 implementation
- WebDAV Class 1 implementation
- built-in SSL/TLS support
- IP-based and name-based virtual hosts
- customizable authentication and authorization
- standard and custom HTTP log formats
- extensible session management
- Basic and Form-based HTTP authentication
- automatic deploying of WAR archives
- runtime server configuration
- full documentation with guides and tutorials
- web application examples with source code

SrvReport is a simple and featurefull server monitoring and reporting system. SrvReport project can send every day a mail with the latest state of the server including:
- network traffic report
- cpu usage report
- mail send/receive
- server warnings
- last logins
- other customized messages (like harddisk problems)
- web-server traffic report
- Xfer-logs (ftp)
- optional test for rootkits (with chkrootkit)
Main features:
A full report will show you the following information:
- Network traffic (including dayly, weekly and monthly graph)
- CPU-Usage (including dayly, weekly and monthly graph)
- Mail sent/receive report (to, from, size)
- Last authenticated users
- Server warnings
- Other customized messages (like harddisk problems)
- Optional web-server traffic report
- Optional Xfer-logs
- Optional test for rootkits (with chkrootkit)
It supports the following features as well:
- Several languages
- No need of rare perl libraries
- Easy to use (Just one configuration file to edit),
- Free (GNU GPL), with sources (perl scripts),

HttpdBase4J is an embeddable Java web server framework that supports HTTP, HTTPS, templated content and serving content from inside an archive.

The classes are easy to extend as they utilize the Hollywood dont call us, well call you principle to allow the user to overide the framework behaviour during all the different phases of the HTTP transaction.

Note:HttpdBase4J uses the Java 6 com.sun.net.httpserver classes so it wont currently work under earlier versions of Java.

Usage Examples:

The simplest use case is to create an embedded web server on port 8088 with its home directory at htdocs in the local filesystem and a root url at / ie / maps onto htdocs:

homeDir = new java.io.File("./htdocs");
httpd = new FileHttpd(homeDir, 10); // Creates a server with a threadpool of 10
httpd.setLogger(System.err); // Log to console
httpd.start(8088, "/");

Creating a HTTPS server equivalent the the HTTP server above requires passing a keystore and password to start. Passing null will generate a certificate free keystore if you only need the encryption capabilities of HTTPS and not the certificate capability:

httpd = new FileHttpd(homeDir, 10);
m_httpd.start(8089, "/", keystore, password);

Serving content from inside an archive or from a jar or zip in the Java classpath requires creating an ArchiveHttpd instance instead of a FileHttpd. To serve content located in a jar or zip in the class path you need only specify the resource directory in the classpath where the content islocated, for example:

httpd = new ArchiveHttpd("/resources/htdocs", 10);
httpd.start(8088, "/");

To serve content from within a specific archive specify the archive as a Java File when constructing the ArchiveHttpd:

httpd = new ArchiveHttpd(new File("content.zip"), "/resources/htdocs", 10);
httpd.start(8088, "/");

Creating web content using templates is also supported. Currently only the StringTemplate library (http://www.stringtemplate.org) is is supported but it should be relatively easy to create user derived classes for other template implementations. To create an HTTP embedded web server on serving templated content from resources/htdocs in the classpath and having a template file handler (A Java class implenting the Templatable interface that is used to fill the templates) in net.homeip.donaldm.test.templates.

httpd = new ArchiveHttpd("resources/htdocs", 10);

StringTemplateHandler stHandler = new ArchiveStringTemplateHandler(httpd,
"net.homeip.donaldm.test.templates");

httpd.addHandler(".st", stHandler); // .st extension = template files
httpd.start(m_port, "/");

The HTTP transaction handling can be customized at any point by overiding any of the methods in the HttpHandleable interface or by overiding onCreateRequestHandler in Httpd in order to provide your own request handler. A simple example of overiding HttpHandleable methods:

httpd = new TestOverideHttpd(m_homeDir, 10);
httpd.start(m_port, "/");

class TestOverideHttpd extends FileHttpd
{
public HttpResponse onServeHeaders(long id, HttpExchange ex, Request request)
{
//Create or amend content
}
public InputStream onServeBody(long id, HttpExchange ex, Request request)
{
//Return amended or created content
}
}