Search Results for: HTTP

How to Track performance with HTTP Archive

Here come one of the best tool to track your website performance.The HTTP Archive is possible through the support of these sponsors: Google, Mozilla, New Relic, O’Reilly Media, Etsy, Strangeloop, and dynaTrace Software. HTTP Archive generates regular reports illustrating trends such as page size and Page Speed score of the top pages on the web. Interested(…)

A complete List of lighttpd Configuration Options

`configure’ configures lighttpd 1.4.28 to adapt to many kinds of systems. Usage: ./configure [OPTION]… [VAR=VALUE]… To assign environment variables (e.g., CC, CFLAGS…), specify them as VAR=VALUE. See below for descriptions of some of the useful variables. Defaults for the options are specified in brackets. Configuration: -h, –help display this help and exit –help=short display options(…)

What Lighttpd is?

What is Lighttpd? Lighttpd, or Lighty, as it is affectionately called, is an extensible, modular, low-footprint, single-threaded, high performance, web server that will happily run on small servers, and outperform an Apache server or Microsoft IIS in most settings. Lighttpd powers many large sites, such as the YouTube video download servers and the image upload(…)

How to Verify That RPC over HTTP Support Is Installed

To verify that RPC over HTTP support is installed Make sure that the ValidPorts registry entry is configured correctly and that the RPC over HTTP component is installed on the Exchange 2003 computer. Additionally, view the application log in Event Viewer. If the ValidPorts registry entry is configured incorrectly, the Rpcproxy.dll file will not load when a client(…)

Curl-loader- A powerful HTTP/HTTPS/FTP/FTPS loading and testing open-source tool

Curl-loader is an open-source tool written in C-language, simulating application load and application behavior of thousands and tens of thousand HTTP/HTTPS and FTP/FTPS clients, each with its own source IP-address. In contrast to other tools curl-loader is using real C-written client protocol stacks, namely, HTTP and FTP stacks of libcurl and TLS/SSL of openssl, and simulates user behavior with(…)

HTTP File Server- A user friendly file server software with a drag and drop interface

HTTP File Server is a free web server specifically designed for publishing and sharing files. The complete feature set differs from other web servers. It’s different from classic file sharing because it uses web technology to be more compatible with today’s Internet. It also differs from classic web servers because it’s very easy to use and runs “right out-of-the(…)

lighttpd- Resource sparing but also fast and full featured HTTP Server

lighttpd is an open-source web server more optimized for speed-critical environments than common products while remaining standards-compliant, secure and flexible. Security, speed, compliance, and flexibility — all of these describe lighttpd -which is rapidly redefining efficiency of a webserver; as it is designed and optimized for high performance environments. With a small memory footprint compared to other web-servers,(…)

Apache Module mod_suexec – Apache HTTP Server

This module, in combination with the suexec support program allows CGI scripts to run as a specified user and Group. The SuexecUserGroup directive allows you to specify a user and group for CGI programs to run as. Non-CGI requests are still processes with the user specified in theUser directive. This directive replaces the Apache 1.3 configuration of using the User(…)

How to Minimize HTTP Requests

80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. Reducing the number of components in turn reduces the number of HTTP requests required to render the page. This is the key to faster pages.(…)

HTTP status codes – A complete list of HTTP status codes

1xx (Provisional response) Status codes that indicate a provisional response and require the requestor to take action to continue. Code Description 100 (Continue) The requestor should continue with the request. The server returns this code to indicate that it has received the first part of a request and is waiting for the rest. 101 (Switching(…)