 | ISAPIZip Documentation |
| | | |
Introduction to ISAPIZip
Getting Started - (Installation Procedures)
Running the Setup Wizard
Configuring IIS Using ISAPIZip
Configuring IIS Manually
Files to be Installed
Feature List
Configuration
User Interface
QuickStart
Compression
URL Filters
MIME Filters
Advanced
License
Manual Configuration Via Config File
Using Header Controls
Dynamic Scriptable Statistics
Frequently Asked Questions
Uninstalling
System Requirements
Release Notes
Licensing/Purchasing
Technical Support
Contact Information
Your web server is sucking your bank account dry!
If your web server is one of the many that requires a lot of bandwidth to deliver quality content to customers visiting your web site, you're spending too much. You see, the more bandwidth a server uses to operate, the more expensive it is to run - and the more money you spend.
With ISAPIZip, you don't have to reduce the quality of your content to reduce your bandwidth costs. ISAPIZip is an Internet Server Application Programming Interface (ISAPI) filter for Internet Information Server (IIS) that compresses data requested from a web server, which reduces the bandwidth required to transfer the data. And, since ISAPIZIP reduces the bandwidth, it also reduces your costs.
ISAPIZip takes advantage of the latest technology built into most web browsers and uses that technology to compress data before it is sent to your web site visitors. When your customer visits your web site, ISAPIZip determines if the browser is capable of accepting compressed material. If it does not, ISAPIZip will not compress the data. If it does, ISAPIZip compresses the data and sends it to the customer. When the customer's browser recieves the data, the data automatically decompresses and your customer sees all of the high quality information you have to offer. And, here's an added benefit - they'll see it faster because ISAPIZip makes web pages load faster!
Very simply, you save money and your customer saves time!
ISAPIZip compresses data to as little as 70% of its original size, which means it reduces bandwidth use by 30%. When bandwidth use is reduced, your costs are reduced - but your quality isn't. In fact you can use the extra bandwidth to serve more quality content while still reducing costs.
While you're saving money, your customers will save time. It's a fact that compressed data loads faster than uncompressed data. As a result, your customers will spend less time waiting for your site to load, making their visit to your site more enjoyable. (And, let's face it, if they enjoyed the visit, they'll probably come back for more!)
ISAPIZip uses a setup wizard to make the installation process as easy as possible. The next four sections will help you run the setup wizard, configure IIS to use ISAPIZip, and provide you a list of files that are installed.
To run the setup wizard for ISAPIZip:
- Double click on the setup file to display the setup program. A screen titled "Welcome to ISAPIZip Setup Wizard" will appear and ask you to verify that you want to install ISAPIZip.
- Click "Next" to continue the setup.
- You will be asked to select a destination or installation directory. Click "Next" to continue setup. (Note: ISAPIZip's default installation destination is "C:\Program Files\ISAPIZip\". However, you can install it in any directory you specify.)
- Click "Install" to confirm that ISAPIZip is to be installed on the computer and finalize the customization of the ISAPIZip installation.
- When the installation is complete, a screen titled "Completing the ISAPIZip Setup Wizard" will appear. The screen includes two checkboxes: "Auto-configure IIS to work with ISAPIZip" and "Launch ISAPIZip." Selecting the Auto-configure box will allow the setup program to prepare IIS to immediately begin working with ISAPIZip. (Note: It is best to restart after the setup is complete.) However, if you choose to leave the Auto-configure box unchecked, you may use the configuration tool later to manually configure or auto-configure ISAPIZip to work with IIS.
- Click "Finish" to close the setup program.
To set up IIS to work with ISAPIZip:
- Open the ISAPIZip configuration tool.
- Click on the QuickStart tab near the top of the window.
- Click the "Add to Webserver" button. (Note: If this button is disabled, it means that IIS is already configured to work with ISAPIZip. To remove the ISAPIZip configuration in IIS click on the "Remove from Webserver" button. This will stop IIS from running ISAPIZip.
IIS can be configured manually to work with ISAPIZip using the following steps:
- Open the Internet Information Services configuration utility. (You can access this utility by opening Control Panel, double-clicking on Administrative Tool, and clicking on Internet Services Manager icon).
- Right-click on the server that ISAPIZip will be installed on and select Properties.
- Under the Internet Information Services tab is a group of options called Master Properties. Click on the "Edit" button and select the ISAPI Filters tab.
- Click on the "Add" button to add ISAPIZip to the list of filters IIS uses.
- In the Filter Properties dialog enter the following information:
- Under Filter Name, enter "ISAPIZip."
- Enter the location of the ISAPIZip DLL file. (Note: The DLL file is is always located in the directory where ISAPIZip was installed "C:\Program Files\ISAPIZip\." To locate the file in Windows Explorer, click "Browse".)
- Click "OK" until you return to the Internet Information Services configuration utility.
- Right-click on the server and select Restart IIS. When the restart is complete, IIS is ready to work with ISAPIZip.
For further step-by-step instructions, visit our Quick Help support area, which shows screenshots of how to install and uninstall an ISAPI plugin with IIS.
The following files are installed during setup and are required to allow ISAPIZip to run properly:
| File Name | Description | | isapizip.exe | ISAPIZip Application | | isapizip.cfg | ISAPIZip Configuration File | | isapizip.dll | ISAPIZip DLL | | isapizip.htm | ISAPIZip Help Documentation | | isapizip-stats.htm | ISAPIZip Scriptable Statistics Example | | elmsg.dll | ISAPIZip Event Log DLL |
All the settings for ISAPIZip can be configured using the ISAPIZip configuration tool. The configuration tool has several tabs: QuickStart, Compression, URL Filters, MIME Filters, Advanced, and License. These tabs provide access to all of ISAPIZip's settings, which make it possible for you to configure ISAPIZip to meet the needs of any web server application.
The "Load" button (located at the bottom of the ISAPIZip application) allows you to load new configuration settings from a configuration file. You can save the configured settings to a configuration file using the "Save" and "Save As" buttons. Use the "Reset" button to reset the current configuration to the ISAPIZip default values. No changes will take effect until they are saved. ISAPIZip periodically checks to see if a new configuration file is available. If the configuration file currently available is newer than the one ISAPIZip has loaded, it will load the new one into memory. one into memory.
When ISAPIZip is started, by default the configuration file that is located in the directory where ISAPIZip was installed (usually "C:\Program Files\ISAPIZip\") is started up as well.
QuickStart is a fast and easy way to configure ISAPIZip. With QuickStart, you can integrate ISAPIZip into IIS with the click of a button.
With this option, it is possible to have ISAPIZip globally start or stop data compression. ISAPIZip will still load in IIS but will cease from compression data that is passed to it. This option is mainly for debug purposes.
Unlike other ISAPI filters for IIS, you can start or stop ISAPIZip from being loaded by IIS using ISAPIZip's configuration tool. ISAPIZip allows for maximum control within IIS without having to adjust the Internet Services Manager settings or manually configure ISAPIZip to work on IIS. Instead, ISAPIZip can configure itself into or out of IIS with minimal effort on your part. To allow the ISAPIZip filter to be loaded by IIS, click on the "Add to Webserver" button. IIS will start using ISAPIZip the next time IIS is restarted or the next time the computer is restarted. To stop the ISAPIZip filter from being loaded by IIS, click on the "Remove from Webserver" button. ISAPIZip will then be removed from use by IIS the next time IIS is restarted or the computer is restarted.
The compression settings for ISAPIZip are located under the Compression tab. These settings give you maximum control over the way ISAPIZip compresses data that is sent to web browsers.
Templates
The compression templates allow you to configure ISAPIZip to meet any compression need. You won't need to know any of the advanced compression settings (located under the ISAPIZip tab) if you use a compression template.
The compression templates are as follows:
- Lowest CPU Usage: Use this template if a web server needs to use the least amount of CPU while still compressing the content that comes to it.
- Smallest Memory Footprint: Use this templateif a web server needs to run with little memory usage.
- Best Compression Ratio: Use this template to provide compression settings for the best compression of all data.
- Best Blended: Use this template to provide compression settings that are optimal for any web server's compression requirements.
Window Size
Control the amount of historical memory available for compressing dynamic content. The higher the value, the more system memory is used to maintain the window. The default value for dynamic historical memory is 15.
Level
Control the amount of compression or the compression level used on the window. The higher the value, the better data is compressed, but with higher CPU usage. The default dynamic compression level is 7.
Memory
Control the amount of memory used when compressing data at a given time. The higher the value, the more memory will be used, but with higher compression results. The default value for dynamic compression memory is 8.
Strategy
Control the compression strategy used while compressing data. - Filtered Strategy: Best used for data consisting mostly of small values with somewhat random distribution.
- Huffman Strategy: Forces Huffman-only matching with no string matching.
- Best Blended Strategy: The best blending of the two compression strategy approaches. Best Blended is the default setting because it provides the best compression.
Using URL filters, ISAPIZip decides whether each file should or should not be compressed based upon that file's content name. URL filters are another way to provide selective compression on content via the content's Filename, Path, Extension, or URL.
URL filters are important, for example, if a web server is required to compress all content except for content inside a particular user's directory. It is possible to do this by adding a Path URL Filter to skip compression based on the user's path on the web server. If a web server needs to compress all file types except for cascading style sheets, it is possible to simply add an Extension URL Filter in which the .css extension is specified as a file extension to skip compression on.
The URL Filters tab lists all the URL filters that ISAPIZip will use to decide whether or not to compress data. The "Add", "Edit", "Remove", and "Reset" buttons allow you to modify URL filters or to create new ones.
To create a new filter item, click on the "Add" button located at the bottom of the screen. The Properties dialog will appear; this is where you will enter all properties of the new filter you want to create. Each filter you create will determine under what circumstances ISAPIZip should operate.
Action
The Action property allows you to specify the action that ISAPIZip should take on this particular filter. The available options for Action are Skip and Compress. Skip will skip compression on any content that the filter matches and Compress will compress any content that the filter matches.
Type
The Type property expresses the type of URL filter being applied. The available selections are Filename, Path, Extension, and URL.
String
The String property is the filter string that will be matched against all content that ISAPIZip handles.
Expect dangling headers (ColdFusion 4/5)
This option fixes problems produced by ColdFusion 4 & 5 where it will split the HTTP headers so that some of the headers appear visible in the user's browser. You can apply this option to specific file extensions (ie: cfm) or files to correct the bug produced by ColdFusion. This problem does not occur in ColdFusion 6/MX. Apply this fix only to file extensions where a problem with ColdFusion headers occurs.
Examples
To skip compression on exe files, use:
Action: Skip
Type: Extension
String: EXE
(Note: If you need compression to occur specifically on exe files, where it normally would not, select Compress as the Action.)
To apply a filter that allows compression on mywebpage.html (where normally it would not) enter in the Filter Properties dialog:
Action: Skip
Type: Filename
String: mywebpage.html
To skip compression on /john/index.html select:
Action: Skip
Type: Path
String: /john/index.html
To fix header problems on ColdFusion 4&5:
Action: Compress
Type: Extension
String: cfm
Check "Expect dangling headers (ColdFusion 4/5)"
To edit an item that has already been added, select the item in the list and click the "Edit" button, or just double click on the item. The Properties dialog will appear with the item's information already entered. Change the information that needs changing and click "OK" to modify the item, or click Cancel to discard any changes.
To remove an item from the list of active filters, select the filter and click the "Remove" button. To clear all of the filters from the list, use the "Reset" button.
MIME Types represent file types as presented to a web browser. When a user requests a file from a web server, the web server sends back a content header in which the file type or the MIME type of the data is noted. This tells the web browser how to handle the data being sent. MIME Filters provide selective compression based on the file's content type, where as URL Filters provide selective compression based upon the file's content name.
For example, the MIME type that is sent to the web browser is usually "text/html" for HTML files, or "text/plain" for TXT files. If the web server needs to ensure that compression did not occur on all plain text files (such as .txt, .log, .c, .cpp, .h, and .ini), it is easier to add a plain text MIME filter instead of adding the various plain text file extensions in the URL Filters tab. Or, if the webserver needs to ensure that any type of application was not compressed, it is easier to add an application MIME filter instead of adding the extensions .com, .exe, etc.
The MIME Filters section contains all the active MIME filters currently being applied when ISAPIZip handles any kind of content. The "Add", "Edit", "Remove", and "Reset" buttons allow the modification of MIME filters or the creation of new ones.
To create a new filter item, click on the "Add" button located at the bottom of the screen. The Properties dialog will appear; this is where you will enter all properties of the new filter you want to create. Each filter you create will determine under what circumstances ISAPIZip should operate.
Action
The Action property allows you to specify the action that ISAPIZip should take on this particular filter. The available options for Action are Skip and Compress. Skip will skip compression on any content that the filter matches and Compress will compress any content that the filter matches.
String
String defines the content type of the file, also known as the MIME type of the content.
Expect dangling headers (ColdFusion 4/5)
This option fixes problems produced by ColdFusion 4 & 5 where it will split the HTTP headers so that some of the headers appear visible in the user's browser. You can apply this option to specific mime types to correct the bug produced by ColdFusion. This problem does not occur in ColdFusion 6/MX. Apply this fix only to mime types where a problem with ColdFusion headers occurs.
Examples
To skip compression on all files matching the MIME type "application" or to stop ISAPIZip from compressing on any applications, enter the following information in the Filter properties dialog:
Action: Skip
String: application
To do the same for all plain text content, use the MIME type "text/plain" and enter the following information:
Action: Skip
String: text/plain
To edit an item that has already been added, select the item in the list and click the "Edit" button, or just double click on the item. The Properties dialog will appear with the item's information already entered. Change the information that needs changing and click "OK" to modify the item, or click Cancel to discard any changes.
To remove an item from the list of active filters, select the filter and click the "Remove" button. To clear all of the filters from the list, use the "Reset" button.
The Advanced tab provides control for ISAPIZip's more advanced features, including support for header controls, real-time statistics, proxy servers, HTTP/1.0 requests, and streamed content. Below are in-depth descriptions about these advanced features.
ISAPIZip provides support for compression requests from proxy servers. By default, this option is turned off because some proxy servers cannot properly handle compressed data.
This feature allows you to control the compression settings per-page using headers scripted into the page at question. These header controls can be placed within any ASP or PHP generated page. With header controls it is possible to change whether or not compression should occur on the page and also what compression window, level, memory, and strategy ISAPIZip should use on the page.
ISAPIZip provides support for browsers that make a request for compressed content using the HTTP/1.0 specification. By default, this option is turned off because compression was not initially part of the HTTP/1.0 specification.
With ISAPIZip you can enable compression support for chunked encoding. Chunked encoding makes it possible to safely transport messages that are sent through the HTTP protocol. ISAPIZip has the ability to compress the chunked data that is sent and ensure that your pages are transported safely
ISAPIZip provides compression for streamed content. When a machine receives streamed content, the flow of chunks sent in and the content does not contain a specific content length. In this case, compression occurs on each streamed chunk that is processed. By default, this option is turned on.
ISAPIZip allows real-time statistics to be generated, which can then be scripted into any web page. Normally, scripting statistics are active for all html pages. To limit the ability to script statistics to a particular file enter in the filename the area provided under the heading "Limit scripting to this file only." Since the statistics are in real-time, they are only visible when compression is turned on and are reset each time the server is restarted. To get dynamic scriptable statistics to work, there is an example file called isapizip-stats.htm included in your ISAPIZip program folder. Move this file anywhere on your web server. Then enter in isapizip-stats.htm in the "Limit scriping to this file only" field. Then from there you can access the scriptable statistics via http://localhost/isapizip-stats.htm if you have placed the isapizip-stats.htm file in the root folder of your web server.
With the Start/Stop Notification feature you can have ISAPIZip put a notification in the Windows Event Log each time ISAPIZip starts or stops.
This feature allows you to control the minimum file size (in bytes) that ISAPIZip will compress. If any files are smaller than the specified size, they will not be compressed. This is useful in cases where the file is so small that it is not worth compressing. The Minimum File Size option does not apply to content where the file size or content length is unknown, such as dynamic and streamed content. The default value is 256 bytes.
With this feature, you can specify the maximum file size (in bytes) for ISAPIZip to compress. Any files that exceed this size will not be compressed. If your maximum file size is set too large, it will enable the compression of very large files which can actually decrease performance because of the time it takes to compress such large files. The larger the file, the more time it takes to compress it. The Maximum File Size option does not apply to content where the file size or content length is unknown, such as dynamic and streamed content.
This feature allows the generation of log files in the supplied log file directory. The log files contain information on all the operations that ISAPIZip performs. By default, this feature is turned off.
Each time a log file is generated, it is generated in a particular format. This format always begins with the date and time the event occurred, followed by the description of the event. For example:
12/14/2003 17:34:52 New configuration applied
This states that a new configuration was applied on 12/14/2003 at 17:34:52. The most important event that is displayed in the log is:
12/14/2003 17:28:49 85116 -> 23415 [86.22MS:Queued:gzip] /drdos.html
The description for this event shows the uncompressed size of the file, what the file was compressed to, how long the file took to compress, whether or not the file was queued or streamed, the compression method, and the file compressed.
A log file record is also kept each time ISAPIZip starts up or shuts down. The format for such an event looks like:
12/12/2003 19:08:30 ISAPIZip v0.8 (Beta) started
12/12/2003 19:08:31 ISAPIZip v0.8 (Beta) shutdown
The description of this event displays the date and time of the event, the name of the ISAPI plugin, the version number, and whether or not a start up or shutdown event occurred.
The License tab provides information about the current copy of ISAPIZip, including the version number, the number of ISAPIZip copies that have been used, and the number of copies that can still be used with the current serial number.
It is possible to configure ISAPIZip manually by editing the configuration (.cfg) file for ISAPIZip, which is located in the directory where ISAPIZip was installed. This is recommended for advanced users only. The configuration file can be edited by loading it into notepad. The format is similar to the format for Windows INI files. After changes have been made to the file and the isapizip.cfg file is saved, ISAPIZip will automatically reload the configuration file and use its new settings. Entries that take integers look like this: MinFileSize:1000. Entries that take strings look like this: LogDirectory:"logs" or SupportProxyIP:"TRUE".
Logging
LogEnabled:[TRUE/FALSE] default: FALSE
LogDirectory:[string] default: log-isapizip\
Event Log Notification
NotifyStartStop:[TRUE/FALSE] default: FALSE
Compression
CompressorEnabled:[TRUE/FALSE] default: TRUE
CompressorStrategy:[integer, 0-2] default: 0
CompressorLevel:[integer, 1-9] default: 7
CompressorMemory:[integer, 1-9] default: 8
CompressorWindow:[integer, 9-15] default: 15
MIME Filter
AllowMIME / DenyMIME:[string]
URL Filter
AllowExtension / DenyExtension:[string]
AllowFilename / DenyFilename:[string]
AllowURL / DenyURL:[string]
Advanced
SupportStreamed:[TRUE/FALSE] default: TRUE
SupportProxies:[TRUE/FALSE] default: FALSE
SupportHTTP1.0:[TRUE/FALSE] default: FALSE
HeaderControl:[TRUE/FALSE] default: FALSE
DynamicStatistics:[TRUE/FALSE] default: FALSE
DynamicStatisticsFileName:[string]
MinFileSize:[integer] default: 256
MaxFileSize: [integer] default: 5242880
This feature allows you to control the compression settings per-page as headers scripted into the page at question. These header controls can be placed within any ASP or PHP generated page. With header controls it is possible to change whether or not compression should occur on the page and also what compression window, level, memory, and strategy ISAPIZip should use on the page.
You may bypass or force compression on specific files by modifying the page's HTTP headers. (Note: In order for the following PHP or ASP code to work correctly it must be placed at the very top of the .PHP or .ASP in which it is to be used.)
PHP: <?php header('Compress-Enabled: No'); ?>
ASP: <% Response.AddHeader Compress-Enabled , No %>
Alternatively, specifying compression of a particular page can be done using the headers below:
PHP: <?php header('Compress-Enabled: Yes'); ?>
ASP: <% Response.AddHeader 'Compress-Enabled','Yes' %>
To set the compression strategy for a particular page where the compression strategy is between 0 and 2, use the headers below:
PHP: <?php header('Compress-Strategy: 1'); ?>
ASP: <% Response.AddHeader 'Compress-Strategy','1' %>
(For more information on compression strategy, see the documentation on the compression settings.)
To set the compression level for a particular page where the compression level is between 1 and 9, use the headers below:
PHP: <?php header('Compress-Level: 8'); ?>
ASP: <% Response.AddHeader 'Compress-Level','8' %>
(For more information on compression level, see the documentation on the compression settings.)
To set the compression memory for a particular page where the compression memory is between 1 and 9, use the headers below:
PHP: <?php header('Compress-Memory: 8'); ?>
ASP: <% Response.AddHeader 'Compress-Memory','8' %>
(For more information on compression memory, see the documentation on the compression settings.)
To set the compression window for a particular page where the compression window is between 9 and 15, use the headers below:
PHP: <?php header('Compress-Window: 9'); ?>
ASP: <% Response.AddHeader 'Compress-Window','9' %>
(For more information on compression window, see the documentation on the compression settings.)
ISAPIZip allows real-time statistics to be generated, which can then be scripted into any web page. Normally scripting statistics are active for all html pages. To limit the ability to script statistics to a particular file, enter the filename in the area provided under the heading "Limit scripting to this file only." Since the statistics are in real-time, they are only visible when compression is turned on and are reset each time the server is restarted.
Below is in-depth coverage on the different statistics that are generated by ISAPIZip. See the simple example below for more information on how to script them into an html page or see the stats html example that came with ISAPIZip.
For any of the statistics where Bytes are specified, note that it can be viewed in Bytes, Kilobytes, or Megabytes. For example:
| <!-- DYNAMICSTATS:TotalInBytes --> | displays statistics in Bytes | | <!-- DYNAMICSTATS:TotalInK --> | displays statistics in Kilobytes | | <!-- DYNAMICSTATS:TotalInMegs --> | displays statistics in Megabytes |
Since ISAPIZip supports multiple compression methods such as GZip and Deflate it is possible to retrieve the statistics for compression based on a particular compression method or on all the compression methods total.
Total Hits <!-- DYNAMICSTATS:TotalHits -->
Displays the total number of pages that ISAPIZip has handled.
GZip Hits <!-- DYNAMICSTATS:GZipHits -->
Displays the total number of pages that have been handled using GZip compression.
Deflate Hits <!-- DYNAMICSTATS:DeflateHits -->
Displays the total number of pages that have been handled using Deflate compression.
Data in statistics are those which show the number of bytes sent in to be handled by ISAPIZip. The display can be configured to indicate Bytes, Kilobytes, and Megabytes.
Total In <!-- DYNAMICSTATS:TotalInBytes -->
This shows the total number of bytes sent in to ISAPIZip using both GZip compression and Deflate compression.
GZip In <!-- DYNAMICSTATS:GZipInBytes -->
This shows the total number of bytes sent to ISAPIZip while using GZip compression.
GZip In Percentage <!-- DYNAMICSTATS:GZipInPercentage -->
This figures the percentage of the total inbound bytes that use GZip compression.
Deflate In <!-- DYNAMICSTATS:DeflateInBytes -->
This indicates the total number of bytes sent to ISAPIZip while using Deflate compression
Deflate In Percentage <!-- DYNAMICSTATS:DeflateInPercentage -->
This calculates the percentage of the total inbound bytes that use Deflate compression.
Data out statistics are those that show the number of bytes that have been sent out by ISAPIZip. You can configure Out to display in Bytes, Kilobytes, and Megabytes.
Total Out <!-- DYNAMICSTATS:TotalOutBytes -->
This shows the total number of bytes sent out by ISAPIZip using both GZip compression and Deflate compression.
GZip Out <!-- DYNAMICSTATS:GZipOutBytes -->
This shows the total number of bytes sent out by ISAPIZip while using GZip compression.
GZip Out Percentage <!-- DYNAMICSTATS:GZipOutPercentage -->
This calculates the percentage of the total amount of bytes sent out that are using GZip compression.
Deflate Out <!-- DYNAMICSTATS:DeflateOutBytes -->
This shows the total number of bytes sent out by ISAPIZip while using Deflate compression.
Deflate Out Percentage <!-- DYNAMICSTATS:DeflateOutPercentage -->
This calculates the percentage of the total outbound bytes that use Deflate compression.
Shows statistics for the number of bytes that ISAPIZip has compressed. This can be configured to display in Bytes, Kilobytes, and Megabytes.
Total Compressed <!-- DYNAMICSTATS:TotalCompressedBytes -->
This shows the total amount of bytes that have been compressed using both Gzip compression and Deflate compression.
GZip Compressed <!-- DYNAMICSTATS:GZipCompressedBytes -->
This shows the total amount of bytes that have been compressed using GZip compression.
GZip Compressed Percentage <!-- DYNAMICSTATS:GZipCompressedPercentage -->
The calculates the percentage of the total number of compressed bytes using GZip compression.
Deflate Compressed <!-- DYNAMICSTATS:DeflateCompressedBytes -->
This shows the total amount of bytes that have been compressed using Deflate compression.
Deflate Compressed Percentage <!-- DYNAMICSTATS:DeflateCompressedPercentage -->
This calculates the percentage of the total bytes compressed using Deflate compression.
Shows average statistics for the amount of bytes compressed using ISAPIZip. You can configure Average to display Bytes, Kilobytes, and Megabytes.
Total Average <!-- DYNAMICSTATS:TotalAverageBytes -->
This shows the average amount of bytes compressed using both GZip and Deflate compressions.
GZip Average <!-- DYNAMICSTATS:GZipAverageBytes -->
This shows the average amount of bytes compressed using only GZip compression.
Deflate Average <!-- DYNAMICSTATS:DeflateAverageBytes -->
This shows the average amount of bytes compressed using only Deflate compression.
Shows the accumulated time spent compressing data. You can configure it to display in Seconds and Milliseconds.
| <!-- DYNAMICSTATS:TotalTimeSeconds --> | displays statistics in Seconds | | <!-- DYNAMICSTATS:TotalTimeMS --> | displays statistics in Milliseconds |
Total Time <!-- DYNAMICSTATS:TotalTimeSeconds -->
This shows the total time accumulated for compressing data using both the GZip and Deflate compressions (displayed in Seconds).
GZip Time <!-- DYNAMICSTATS:GZipTimeSeconds -->
This shows the total time accumulated to compress data using GZip compression (displayed in Seconds).
Deflate Time <!-- DYNAMICSTATS:DeflateTimeSeconds -->
This shows the total time accumulated to compress data using Deflate compression (displayed in Seconds).
<!-- DYNAMICSTATS:MimeType -->
This function shows the Mime type of the current page.
Current <!-- DYNAMICSTATS:CurrentConnections -->
This indicates the number of connections currently using ISAPIZip.
Maximum <!-- DYNAMICSTATS:MaximumConnections -->
This indicates the maximum number of simultaneous connections that used ISAPIZip.
Shows the accumulated time spent compressing data. You can configure Memory be to displayed in Bytes, Kilobytes, or Megabytes.
Current <!-- DYNAMICSTATS:CurrentMemory -->
This shows the amount of memory currently being used.
Maximum <!-- DYNAMICSTATS:MaximumMemory -->
This shows the maximum amount of memory that has been used.
<!-- DYNAMICSTATS:Version -->
Displays the program name and version information.
<html>
<body>
<font face='arial' size='2'>
<h3>Real-time Statistics for MyWebServer</h3>
<b>Total Hits</b>:
<!-- DYNAMICSTATS:TotalHits --><br>
<b>Total Data Sent In</b>:
<!-- DYNAMICSTATS:TotalInBytes --> bytes<br>
<b>Total Data Sent Out</b>:
<!-- DYNAMICSTATS:TotalOutBytes --> bytes<br>
<b>Total Data Compressed</b>:
<!-- DYNAMICSTATS:TotalCompressedBytes --> bytes<br>
<b>Total Percent of Data Compressed</b>:
<!-- DYNAMICSTATS:TotalCompressedPercentage -->% <br>
<b>Accumulated Time Spent Compressing Data</b>:
<!-- DYNAMICSTATS:TotalTimeSeconds --> seconds<br><br>
Currently compressing data for
<!-- DYNAMICSTATS:CurrentConnections --> users<br>
Currently using
<!-- DYNAMICSTATS:CurrentMemoryK --> KB of Memory<br>
</font>
</body>
</html>
To Uninstall ISAPIZip, click on the Uninstall icon that is located in the Program Folder for ISAPIZip in the Start menu. This will run through the uninstall program and uninstall ISAPIZip. If the ISAPIZip filter is currently in use by IIS, the ISAPIZip DLL file that IIS uses will be deleted the next time the system is restarted.
For further step-by-step instructions, visit our Quick Help support area, which shows screenshots of how to install and uninstall an ISAPI plugin with IIS.
ISAPIZip requires Windows NT/2000/XP Professional/2003 .NET with Microsoft Internet Information Services (IIS) 5.x or 6 and at least 128 MB of RAM.
Version 2.02 - Added support for ColdFusion 5 or eariler as well as chunked encoding
Version 2.01 - Fixed problem with alternative requests
Version 2.00 - Support for IIS6, configuration utility, and more!
Version 1.05 - Added support for streamed content
Version 1.00 - First release of ISAPIZip
For important information on purchasing a copy of ISAPIZip, please contact ISAPILabs at http://www.isapilabs.com/.
All technical support is available via our support page located on the World Wide Web at http://www.isapilabs.com/.
To contact us, please visit our contact page.
|
|
|
|
