HTTP compression
From Wikipedia, the free encyclopedia
(Redirected from Http compression)
 |
This article does not cite any references or sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (August 2008) |
| HTTP |
| Persistence · Compression · HTTP Secure |
| Headers |
| ETag · Cookie · Referrer · Location |
| Status codes |
| 301 Moved permanently |
| 302 Found |
| 303 See Other |
| 403 Forbidden |
| 404 Not Found |
HTTP compression is a capability built into both web servers and web browsers, to make better use of available bandwidth. HTTP protocol data is compressed before it is sent from the server: compliant browsers will announce what methods are supported to the server before downloading the correct format; unsupported browsers will download uncompressed data. Data is usually compressed with either deflate or gzip modules specific to the server software.
[edit] Servers that support HTTP compression
- Microsoft IIS: built-in or using 3rd-party module
- Apache HTTP Server, via mod_deflate or mod_gzip
- Caucho Resin Professional, via GzipFilter
- Sun Java System Web Server
- Zeus Web Server
- Lighttpd, via mod_compress[1]
- Nginx - built-in
- RaidenHTTPD - built-in
- Serenity Server - built-in.
[edit] External links
- RFC 2616
- Apache: mod_deflate & mod_gzip
- Compression with lighttpd
- 15 Seconds: Web Site Compression
- HTTP Compression: resource page by the founder of VIGOS AG, Constantin Rack
- Using HTTP Compression by Martin Brown of Server Watch
- Using HTTP Compression in IIS 6.0: Microsoft page
- Enabling HTTP Compression in IIS 6.0: detailed article from Donnie Mack of DotNetJunkies
[edit] Notes
- ^ Lighttpd's mod_compress only supports compressing static files, that is, no content dynamically generated from a cgi/fcgi/other program. mod_deflate is a modified version of mod_compress which supports dynamic content compression but it's planned for Lighttpd 1.5.0 which is still under development.
