what does http stand for
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 3127
Apache HTTP Server for Linux 2.0.52
Generation 2.x of the most popular HTTP server on the net. more>>
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.
<<lessApache 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.
Download (6.6MB)
Added: 2009-04-01 License: Freeware Price:
219 downloads
Other version of Apache HTTP Server for Linux
Price: FREE
License:Freeware
License:Freeware
License:Freeware
WebInject - Web/HTTP Test Tool 1.35
WebInject is a tool for automated testing of web applications and services. more>>
WebInject is a free tool for automated testing of web applications and services. It can be used to test individual system components that have HTTP interfaces (JSP, ASP, CGI, PHP, Servlets, HTML Forms, etc), and can be used as a test harness to create a suite of [HTTP level] automated functional, acceptance, and regression tests. A test harness, also referred to as a test driver or a test framework, allows you to run many test cases and collect/report your results. WebInject offers real-time results display and may also be used for monitoring system response times.
WebInject can be used as a complete test framework that is controlled by the WebInject User Interface (GUI). Optionally, it can be used as a standalone test runner (text/console application) which can be integrated and called from other test frameworks or applications.
WebInject uses an XML API (interface). This means you can use WebInject without ever seeing its internal implementation (no scripting or programming necessary to use it).
WebInject is written in Perl and can run on any platform that a Perl interpreter can be installed on (MS Windows, GNU/Linux, BSD, Solaris, MAC OS, and many more). Currently, binary executables of WebInject are only available for MS Windows. If you would like to run on other platforms, you must have a Perl interpreter and run it from the Perl source code.
Test cases are written in XML files, using XML tags and attributes, and passed to the WebInject engine for execution against the application/service under test. This abstracts the internals of WebInjects implementation away from the non-technical tester, while using an open architecture [written in Perl] for those that require more customization or modifications.
Result reports are generated in HTML (for viewing) and XML (for tranformation by external programs). These detailed results include pass/fail status, errors, response times, etc. Results are also displayed in a window on the User Interface if you are running the WebInject GUI, and are sent to the STDOUT channel if you are running the WebInject Engine as a standalone (console) application.
HTTP response times can be collected and monitored in real-time during test execution. Timer statistics are calculated and displayed in a monitor window during runtime. When used along with gnuplot (a plotting utility), a response time graph is generated and updated in real-time as the test runs. This is used to verify responses from the application/service under test are within an acceptable range (to meet your SLA or quality of service criteria). This also enables WebInject to be run as a performance probe for application/service monitoring.
<<lessWebInject can be used as a complete test framework that is controlled by the WebInject User Interface (GUI). Optionally, it can be used as a standalone test runner (text/console application) which can be integrated and called from other test frameworks or applications.
WebInject uses an XML API (interface). This means you can use WebInject without ever seeing its internal implementation (no scripting or programming necessary to use it).
WebInject is written in Perl and can run on any platform that a Perl interpreter can be installed on (MS Windows, GNU/Linux, BSD, Solaris, MAC OS, and many more). Currently, binary executables of WebInject are only available for MS Windows. If you would like to run on other platforms, you must have a Perl interpreter and run it from the Perl source code.
Test cases are written in XML files, using XML tags and attributes, and passed to the WebInject engine for execution against the application/service under test. This abstracts the internals of WebInjects implementation away from the non-technical tester, while using an open architecture [written in Perl] for those that require more customization or modifications.
Result reports are generated in HTML (for viewing) and XML (for tranformation by external programs). These detailed results include pass/fail status, errors, response times, etc. Results are also displayed in a window on the User Interface if you are running the WebInject GUI, and are sent to the STDOUT channel if you are running the WebInject Engine as a standalone (console) application.
HTTP response times can be collected and monitored in real-time during test execution. Timer statistics are calculated and displayed in a monitor window during runtime. When used along with gnuplot (a plotting utility), a response time graph is generated and updated in real-time as the test runs. This is used to verify responses from the application/service under test are within an acceptable range (to meet your SLA or quality of service criteria). This also enables WebInject to be run as a performance probe for application/service monitoring.
Download (0.029MB)
Added: 2005-04-12 License: GPL (GNU General Public License) Price:
1662 downloads
Java Lemonade Stand 1.3
Java Lemonade Stand is a lemonade stand game. more>>
Java Lemonade Stand is a lemonade stand game. To play the game, click on the link below.
You are the sole proprietor of a lemonade stand in your front yard. Your parents were kind enough to knock together a booth and provide some initial capital and supplies.
You have three months to make as much money as possible. Placing money in the bank is a good idea. You earn interest.
The left side of the display contains four tabs (Prepare for Sale, Finances, Inventory, and Advertising) for managing your advertising and assets. The left side displays sales results and weather forecasts. Check the weather forecast then decide how much advertising to purchase, how many cups to make, and how much to charge. Press the Sell Lemonade button to see how you fared.
Prepare for Sale
Here you decide what quality of lemonade mix to use (Generic, Name Brand, or Premium), how many cups of lemonade to prepare, and how much to charge for each cup. Using a higher quality of lemonade will positively impact the price customers will pay and the number of cups they will purchase.
Finances
Your money is divided into working cash and a savings account. Purchases for supplies and advertising are deducted from your working cash. Profits from your lemonade sales will be added to your working cash. You can transfer money between your working cash and savings account. You will receive interest on your savings account at the end of each month. The interest is based on your average daily balance.
Inventory
Your inventory consists of lemonade mix and cups. Buying in larger quantities is more cost-effective. You can only make and sell as much lemonade as you have mix and cups. Lemonade mix comes in different levels of quality: Generic, Name Brand, and Premium. Higher quality lemonade costs more.
Advertising
Advertising helps to bring more customers to your stand. Notice that some types of advertising last multiple days while others only last for a day. Homemade signs last a variable period of time.
Weather
Weather has a significant impact on the number of customers that come to your stand and the amount that they will pay for your lemonade. You will receive a forecast for the next days weather each day. This forecast is somewhat accurate but not 100% reliable. The eight types of weather are listed below.
Sunny and Scorching: Ideal conditions.
Sunny and Hot
Sunny and Warm
Sunny
Party Sunny
Overcast
Rain
Thunderstorms: Worst conditions.
Sales Results
Here you will see the weather for the day, the number of customers who visited your stand, the number of cups you sold, and your gross and net profit. You will also learn about any random events that might impact your business.
<<lessYou are the sole proprietor of a lemonade stand in your front yard. Your parents were kind enough to knock together a booth and provide some initial capital and supplies.
You have three months to make as much money as possible. Placing money in the bank is a good idea. You earn interest.
The left side of the display contains four tabs (Prepare for Sale, Finances, Inventory, and Advertising) for managing your advertising and assets. The left side displays sales results and weather forecasts. Check the weather forecast then decide how much advertising to purchase, how many cups to make, and how much to charge. Press the Sell Lemonade button to see how you fared.
Prepare for Sale
Here you decide what quality of lemonade mix to use (Generic, Name Brand, or Premium), how many cups of lemonade to prepare, and how much to charge for each cup. Using a higher quality of lemonade will positively impact the price customers will pay and the number of cups they will purchase.
Finances
Your money is divided into working cash and a savings account. Purchases for supplies and advertising are deducted from your working cash. Profits from your lemonade sales will be added to your working cash. You can transfer money between your working cash and savings account. You will receive interest on your savings account at the end of each month. The interest is based on your average daily balance.
Inventory
Your inventory consists of lemonade mix and cups. Buying in larger quantities is more cost-effective. You can only make and sell as much lemonade as you have mix and cups. Lemonade mix comes in different levels of quality: Generic, Name Brand, and Premium. Higher quality lemonade costs more.
Advertising
Advertising helps to bring more customers to your stand. Notice that some types of advertising last multiple days while others only last for a day. Homemade signs last a variable period of time.
Weather
Weather has a significant impact on the number of customers that come to your stand and the amount that they will pay for your lemonade. You will receive a forecast for the next days weather each day. This forecast is somewhat accurate but not 100% reliable. The eight types of weather are listed below.
Sunny and Scorching: Ideal conditions.
Sunny and Hot
Sunny and Warm
Sunny
Party Sunny
Overcast
Rain
Thunderstorms: Worst conditions.
Sales Results
Here you will see the weather for the day, the number of customers who visited your stand, the number of cups you sold, and your gross and net profit. You will also learn about any random events that might impact your business.
Download (0.28MB)
Added: 2006-12-05 License: GPL (GNU General Public License) Price:
1058 downloads
HTTP extension for PHP 1.5.4
HTTP extension for PHP allows building absolute URIs. more>>
HTTP extension for PHP allows building absolute URIs, RFC-compliant HTTP redirects, RFC-compliant HTTP date handling, parsing of HTTP headers and messages, caching by "Last-Modified" and/or ETag (with an on the fly option for ETag generation from buffered output), sending data/files/streams with (multiple) ranges, negotiating user-preferred language/charset, and convenient request functionality built upon libcurl.
PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, and HttpMessage.
Main features:
- Building absolute URIs
- RFC compliant HTTP redirects
- RFC compliant HTTP date handling
- Parsing of HTTP headers and messages
- Caching by "Last-Modified" and/or ETag (with on the fly option for ETag generation from buffered output)
- Sending data/files/streams with (multiple) ranges support
- Negotiating user preferred language/charset
- Convenient request functionality built upon libcurl
- PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, HttpMessage.
Enhancements:
- This release fixes bug #11359: HttpMessage::toMessageTypeObject() does not populate POST fields.
<<lessPHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, and HttpMessage.
Main features:
- Building absolute URIs
- RFC compliant HTTP redirects
- RFC compliant HTTP date handling
- Parsing of HTTP headers and messages
- Caching by "Last-Modified" and/or ETag (with on the fly option for ETag generation from buffered output)
- Sending data/files/streams with (multiple) ranges support
- Negotiating user preferred language/charset
- Convenient request functionality built upon libcurl
- PHP5 classes: HttpUtil, HttpResponse (PHP-5.1), HttpRequest, HttpRequestPool, HttpMessage.
Enhancements:
- This release fixes bug #11359: HttpMessage::toMessageTypeObject() does not populate POST fields.
Download (0.16MB)
Added: 2007-06-29 License: BSD License Price:
851 downloads
Monkey HTTP Daemon 0.9.1
Monkey is a Web server written in C that works under Linux. more>>
Monkey is a Web server written in C that works under Linux. This is an open source project based on the HTTP/1.1 protocol.
The objective is to develop a fast, efficient, small and easy to configure web server. If you wish to contribute to this project as a beta-tester, submitting suggestions and constructive criticisms, just contact me. Your input is welcome.
Main features:
- Get, Post & Head method
- CGI & PHP
- Multithreading
- Config files
- Mime types
- VirtualHost
- Directories navigation
- Users home
- Deny by URL & IP
- Resume
<<lessThe objective is to develop a fast, efficient, small and easy to configure web server. If you wish to contribute to this project as a beta-tester, submitting suggestions and constructive criticisms, just contact me. Your input is welcome.
Main features:
- Get, Post & Head method
- CGI & PHP
- Multithreading
- Config files
- Mime types
- VirtualHost
- Directories navigation
- Users home
- Deny by URL & IP
- Resume
Download (0.082MB)
Added: 2005-09-05 License: GPL (GNU General Public License) Price:
1510 downloads
wgrab http file fetcher 1.1.3
wgrab http file fetcher provides a small, fast, and cross platform wget alternative. more>>
wgrab http file fetcher provides a small, fast, and cross platform wget alternative.
wgrab is an HTTP file fetcher similar to wget that is designed to be small, fast, and cross-platform compatible natively. The compiled wgrab is approximately 1/10th the size of wget, making it ideal for distributions like DSL and other miniature distributions.
Enhancements:
- fixed a spelling error in the --help output
- fixed the --timeout help being reported for --ignore-errors
- updated the installer to contain color coded responses if possible
- fixed "Network no reachable" error if no url was specified
<<lesswgrab is an HTTP file fetcher similar to wget that is designed to be small, fast, and cross-platform compatible natively. The compiled wgrab is approximately 1/10th the size of wget, making it ideal for distributions like DSL and other miniature distributions.
Enhancements:
- fixed a spelling error in the --help output
- fixed the --timeout help being reported for --ignore-errors
- updated the installer to contain color coded responses if possible
- fixed "Network no reachable" error if no url was specified
Download (MB)
Added: 2007-03-29 License: GPL (GNU General Public License) Price:
942 downloads
RealizationEngine Desktop Status Checker 0.04
RealizationEngine Desktop Status Checker is a stand alone desktop client to alert you to new messages in RealizationEngine. more>>
rcheck is a tool that will allow you to check the status of one or more accounts on one or more RealizationEngines. rcheck is written in Perl, requires LWP::Simple and Digest::MD5 and Tk.
rcheck is intended to be a demonstration for creating clients that can check for and report new messages.
The status for an account can be requested by the following URL:
http://www.your_re.com/cgi-bin/re_status.cgi?status=username
this will return the results in the form:
total_messages:todays_messages:new_messages
Example: 100:10:2
The results are XORed against the MD5 digest (hex) of the users password before being sent so that the results are "lightly" encrypted. The results are trimmed to the length of the output only.
After receiving the encrypted result string from the server, take the MD5 digest (hex) of the users password, trim it to the same length as the status string and XOR the two against each other. This will give the plaintext of the status message.
rcheck only reports new messages since last session, and the other two numbers are tossed in the trash.
rcheck stores a file called .rcheck2 in the local directory with account information (passwords encrypted).
<<lessrcheck is intended to be a demonstration for creating clients that can check for and report new messages.
The status for an account can be requested by the following URL:
http://www.your_re.com/cgi-bin/re_status.cgi?status=username
this will return the results in the form:
total_messages:todays_messages:new_messages
Example: 100:10:2
The results are XORed against the MD5 digest (hex) of the users password before being sent so that the results are "lightly" encrypted. The results are trimmed to the length of the output only.
After receiving the encrypted result string from the server, take the MD5 digest (hex) of the users password, trim it to the same length as the status string and XOR the two against each other. This will give the plaintext of the status message.
rcheck only reports new messages since last session, and the other two numbers are tossed in the trash.
rcheck stores a file called .rcheck2 in the local directory with account information (passwords encrypted).
Download (0.010MB)
Added: 2005-04-26 License: GPL (GNU General Public License) Price:
1642 downloads
HTTP::Handle 0.2
HTTP::Handle is a HTTP Class designed for streaming. more>>
HTTP::Handle is a HTTP Class designed for streaming.
SYNOPSIS
use HTTP::Handle;
my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();
my $fd = $http->fd();
while () {
print "--> $_";
}
The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.
HTTP::Handle->new()
Create a new HTTP::Handle object thingy.
Arguments possible:
url => "http://www.google.com/"
Sets the initial URL to connect to.
follow_redirects => [ 0 | 1 ]
Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.
http_request => HASHREF
Any thing put in here will be sent as "key: value" in the http request string.
$http->connect()
Connect, send the http request, and process the response headers.
This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.
$http->fd()
Get the file descriptor (socket) were using to connect.
$http->url( [ url_string ])
Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the
$http->follow_redirects( [ 0 | 1 ] )
If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.
Defaults to 1 (will follow redirects).
$http->http_request_string()
Returns a string containing the HTTP request and headers, this is used when
$http->connect() is called.
<<lessSYNOPSIS
use HTTP::Handle;
my $http = HTTP::Handle->new( uri => "http://www.google.com/" );
$http->connect();
my $fd = $http->fd();
while () {
print "--> $_";
}
The HTTP::Handle module allows you to make HTTP requests and handle the data yourself. The general ideas is that you use this module to make a HTTP request and handle non-header data yourself. I needed such a feature for my mp3 player to listen to icecast streams.
HTTP::Handle->new()
Create a new HTTP::Handle object thingy.
Arguments possible:
url => "http://www.google.com/"
Sets the initial URL to connect to.
follow_redirects => [ 0 | 1 ]
Automatically follow HTTP redirects. This defaults to true (1). Set to 0 to disable this.
http_request => HASHREF
Any thing put in here will be sent as "key: value" in the http request string.
$http->connect()
Connect, send the http request, and process the response headers.
This function returns -1 on failure, undef otherwise. The reason for failure will be printed to STDERR.
$http->fd()
Get the file descriptor (socket) were using to connect.
$http->url( [ url_string ])
Get or set the URL. If a url string is passed, you will change the url that is requested. If no parameter is passed, a URI object will be returned containing the
$http->follow_redirects( [ 0 | 1 ] )
If a value is passed then you will set whether or not we will automatically follow HTTP 302 Redirects. If no value is passed, then we will return whatever the current option is.
Defaults to 1 (will follow redirects).
$http->http_request_string()
Returns a string containing the HTTP request and headers, this is used when
$http->connect() is called.
Download (0.005MB)
Added: 2006-11-16 License: Perl Artistic License Price:
1072 downloads
Bauk HTTP server 2.0.5
Bauk HTTP server project is a high-performance Web server. more>>
Bauk HTTP server project is a high-performance Web server. Bauks advanced architecture and unique design provide high performance and many original features, ie. ability to serve unlimited number of Virtual Hosts/simultaneous HTTP connections per single server process without performance loss.
Full installation requires only a single directory of UNIX file system used as a working directory for Bauk executable. Configuration process is simple and performed by adjustment of Bauk configuration script.
Main features:
- Full HTTP/1.1 and CGI/1.1 standard compliance
- HTTP authentication, Basic method, auth script per Virtual Host
- Unlimited number of Virtual Hosts without performance loss
- Virtual Host aliases
- Unlimited number of simultaneous HTTP connections per single Bauk process with no performance loss (Special Edition)
- Persistent (Keep-Alive) connections
- URL Path; define URL and path with type of access; ie. read, write, browse, execute, require HTTP authentication, etc.
- OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE methods of HTTP request defined by HTTP/1.1, configurable per URL Path
- Content negotiation by client language and charset
- Configurable MIME types
- Configurable HTTP headers by MIME type
- Configurable HTML error documents / CGI executables
- Directory browsing; view content of directories with HTML links
- Execution of CGI programs/scripts
- SUID/SGID for CGI execution
- Chroot for CGI execution; chroot CGI to Virtual Hosts home
- 3 security layers for CGI execution: by URL limit to X-only ie. CGI dir; for RX-URL imply X-only for X-able files; impose X-only by file extension ie. CGI executables wrongly placed and no X flag
- Quotas for CGI execution; number of simultaneous CGI processes, execution priority, max execution time (duration), max CPU time, memory, filesize
- Quotas of network traffic in/out per Virtual Host (I/O speed limit)
- Quotas of connections per Virtual Host
- Quotas of connections per client IP number
- Access restriction by IP address; forbid and allow-only
- Access restriction by valid HTTP referrer
- Configurable HTTP-log format and location for Virtual Hosts
- Configurable singleprocess or multiprocess architecture
- Chroot for Bauk server process
- Full configurability; virtually all Bauk features are configurable by simple configuration script adjustment
- Easy configuration by script language; built-in configuration script interpreter with preprocessor, file-inclusion, block and single-line comments, two data types, variables, arithmetic operations and built-in functions
- Easy administration
- Flexibility
VLAJKOS INVISIBLE LICENSE (VIL):
This sofware is protected by VIL and the license states:
Youre welcome to use this software. Remember the rightful author if youre using any parts/unique components of Bauk software.
Enhancements:
- This release includes various feature enhancements
- improved PHP, Perl, Gawk
- Tcl interpreter connectors
- additions to the documentation.
<<lessFull installation requires only a single directory of UNIX file system used as a working directory for Bauk executable. Configuration process is simple and performed by adjustment of Bauk configuration script.
Main features:
- Full HTTP/1.1 and CGI/1.1 standard compliance
- HTTP authentication, Basic method, auth script per Virtual Host
- Unlimited number of Virtual Hosts without performance loss
- Virtual Host aliases
- Unlimited number of simultaneous HTTP connections per single Bauk process with no performance loss (Special Edition)
- Persistent (Keep-Alive) connections
- URL Path; define URL and path with type of access; ie. read, write, browse, execute, require HTTP authentication, etc.
- OPTIONS, GET, HEAD, POST, PUT, DELETE, TRACE methods of HTTP request defined by HTTP/1.1, configurable per URL Path
- Content negotiation by client language and charset
- Configurable MIME types
- Configurable HTTP headers by MIME type
- Configurable HTML error documents / CGI executables
- Directory browsing; view content of directories with HTML links
- Execution of CGI programs/scripts
- SUID/SGID for CGI execution
- Chroot for CGI execution; chroot CGI to Virtual Hosts home
- 3 security layers for CGI execution: by URL limit to X-only ie. CGI dir; for RX-URL imply X-only for X-able files; impose X-only by file extension ie. CGI executables wrongly placed and no X flag
- Quotas for CGI execution; number of simultaneous CGI processes, execution priority, max execution time (duration), max CPU time, memory, filesize
- Quotas of network traffic in/out per Virtual Host (I/O speed limit)
- Quotas of connections per Virtual Host
- Quotas of connections per client IP number
- Access restriction by IP address; forbid and allow-only
- Access restriction by valid HTTP referrer
- Configurable HTTP-log format and location for Virtual Hosts
- Configurable singleprocess or multiprocess architecture
- Chroot for Bauk server process
- Full configurability; virtually all Bauk features are configurable by simple configuration script adjustment
- Easy configuration by script language; built-in configuration script interpreter with preprocessor, file-inclusion, block and single-line comments, two data types, variables, arithmetic operations and built-in functions
- Easy administration
- Flexibility
VLAJKOS INVISIBLE LICENSE (VIL):
This sofware is protected by VIL and the license states:
Youre welcome to use this software. Remember the rightful author if youre using any parts/unique components of Bauk software.
Enhancements:
- This release includes various feature enhancements
- improved PHP, Perl, Gawk
- Tcl interpreter connectors
- additions to the documentation.
Download (0.22MB)
Added: 2007-01-20 License: Other/Proprietary License Price:
1008 downloads
phpautotest 1.0.3
phpautotest is a tool for conducting automated regression tests on PHP-driven Web sites. more>>
phpautotest is a tool for conducting automated regression tests on PHP-driven Web sites. Variable values as well as HTTP output can be tested.
HTTP output is tested using regular expressions.
<<lessHTTP output is tested using regular expressions.
Download (0.18MB)
Added: 2006-05-11 License: MIT/X Consortium License Price:
1264 downloads
Dwarf HTTP Server 1.3.1
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. more>>
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
<<lessDwarf 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
Download (0.91MB)
Added: 2005-12-08 License: Freely Distributable Price:
1415 downloads
darkhttpd 1.7
darkhttpd is a secure, lightweight, fast, single-threaded HTTP/1.1 server for static content. more>>
darkhttpd 1.7 is yet another great addition to your computer. It is actually a secure, lightweight, fast, single-threaded HTTP/1.1 server for static content.
Enhancements:
- Links in directory listings which contain special characters are now URL encoded.
Added: 2008-11-05 License: BSD License Price: FREE
12 downloads
HTTP Anti Virus Proxy 0.86
HTTP Anti Virus Proxy is a proxy with a ClamAV anti-virus scanner. more>>
HAVP (HTTP Antivirus Proxy) is a proxy with a ClamAV anti-virus scanner. HTTP Anti Virus Proxy aims are continuous, non-blocking downloads and smooth scanning of dynamic and password protected HTTP traffic.
Havp antivirus proxy has a parent and transparent proxy mode. It can be used with squid or standalone.
Main features:
- HTTP Antivirus proxy
- Scans complete incomming traffic
- Nonblocking downloads
- Smooth scanning of dynamic and password protected traffic
- Can used with squid or other proxy
- Parent proxy support
- Transparent proxy support
- Logfile
- Process change to defined user and group
- Daemon
- Use Clamav (GPL antivirus)
- Operating System: Linux
- Written in C++
- Released under GPL
Enhancements:
- Experimental support was added for chunked Transfer-Encoding, which fixes some broken sites.
- The IGNOREVIRUS configuration directive was added for whitelisting virus names.
- The CLAMBLOCKBROKEN configuration directive was added.
- Detection with AVG was improved.
- HAVP is killed if database reloading fails for Library Scanner.
- The URL is logged when a crashed scanner process is detected.
- The build system updated, adding the --prefix, --sbindir, --sysconfdir, and --localstatedir options.
<<lessHavp antivirus proxy has a parent and transparent proxy mode. It can be used with squid or standalone.
Main features:
- HTTP Antivirus proxy
- Scans complete incomming traffic
- Nonblocking downloads
- Smooth scanning of dynamic and password protected traffic
- Can used with squid or other proxy
- Parent proxy support
- Transparent proxy support
- Logfile
- Process change to defined user and group
- Daemon
- Use Clamav (GPL antivirus)
- Operating System: Linux
- Written in C++
- Released under GPL
Enhancements:
- Experimental support was added for chunked Transfer-Encoding, which fixes some broken sites.
- The IGNOREVIRUS configuration directive was added for whitelisting virus names.
- The CLAMBLOCKBROKEN configuration directive was added.
- Detection with AVG was improved.
- HAVP is killed if database reloading fails for Library Scanner.
- The URL is logged when a crashed scanner process is detected.
- The build system updated, adding the --prefix, --sbindir, --sysconfdir, and --localstatedir options.
Download (0.53MB)
Added: 2007-04-17 License: GPL (GNU General Public License) Price:
932 downloads
HTTP::Async 0.05
HTTP::Async is a Perl module that can process multiple HTTP requests in parallel without blocking. more>>
HTTP::Async is a Perl module that can process multiple HTTP requests in parallel without blocking.
SYNOPSIS
Create an object and add some requests to it:
use HTTP::Async;
my $async = HTTP::Async->new;
# create some requests and add them to the queue.
$async->add( HTTP::Request->new( GET => http://www.perl.org/ ) );
$async->add( HTTP::Request->new( GET => http://www.ecclestoad.co.uk/ ) );
and then EITHER process the responses as they come back:
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
OR do something else if there is no response ready:
while ( $async->not_empty ) {
if ( my $response = $async->next_response ) {
# deal with $response
} else {
# do something else
{
}
OR just use the async object to fetch stuff in the background and deal with the responses at the end.
# Do some long code...
for ( 1 .. 100 ) {
some_function();
$async->poke; # lets it check for incoming data.
}
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
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.
Whilst it is waiting to receive data it returns control to the code that called it meaning that you can carry out processing whilst fetching data from the network. All without forking or threading - it is actually done using select lists.
<<lessSYNOPSIS
Create an object and add some requests to it:
use HTTP::Async;
my $async = HTTP::Async->new;
# create some requests and add them to the queue.
$async->add( HTTP::Request->new( GET => http://www.perl.org/ ) );
$async->add( HTTP::Request->new( GET => http://www.ecclestoad.co.uk/ ) );
and then EITHER process the responses as they come back:
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
OR do something else if there is no response ready:
while ( $async->not_empty ) {
if ( my $response = $async->next_response ) {
# deal with $response
} else {
# do something else
{
}
OR just use the async object to fetch stuff in the background and deal with the responses at the end.
# Do some long code...
for ( 1 .. 100 ) {
some_function();
$async->poke; # lets it check for incoming data.
}
while ( my $response = $async->wait_for_next_response ) {
# Do some processing with $response
}
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.
Whilst it is waiting to receive data it returns control to the code that called it meaning that you can carry out processing whilst fetching data from the network. All without forking or threading - it is actually done using select lists.
Download (0.015MB)
Added: 2007-01-17 License: Perl Artistic License Price:
1011 downloads

HFS - HTTP File Ser ver 2.3 Build 171 Be
You can use HFS (HTTP File Server) to send and receive files. more>> You can use HFS (HTTP File Server) to send and receive files.
Its different from classic file sharing because it uses web technology to be more compatible with todays Internet.
It also differs from classic web servers because
its very easy to use and runs "right out-of-the box".
Access your remote files, over the network.
It has been successfully tested with Wine under Linux.<<less
Download (550KB)
Added: 2009-04-03 License: Freeware Price: Free
203 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above what does http stand for search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed