Here's a suggestion posted on the NNTP forum; I looks like A Good Thing...
On 20 Oct 2010 00:35:53 -0700, LM wrote:
asked 26 Oct '10, 11:02
I've added this to our "stuff to look into" list. Note that the website linked to doesn't exist - or at least it has no DNS entry.
From Breck: Allow me to retort...
C:\Documents and Settings\bcarter>ping www.http-compression.com Pinging www.http-compression.com [188.8.131.52] with 32 bytes of data: Reply from 184.108.40.206: bytes=32 time=153ms TTL=52 Reply from 220.127.116.11: bytes=32 time=152ms TTL=52 Reply from 18.104.22.168: bytes=32 time=155ms TTL=52 Reply from 22.214.171.124: bytes=32 time=154ms TTL=52 Ping statistics for 126.96.36.199: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 152ms, Maximum = 155ms, Average = 153ms
Strange. Must be a Sybase thing:
[C:\WINDOWS]ping www.http-compression.com Ping request could not find host www.http-compression.com. Please check the name and try again.
http://downforeveryoneorjustme.com/www.http-compression.com says it's up too.
Actually, it is possible so serve compressed HTTP content using current SA versions, but it requires some additional coding (see example below). So, a built-in HTTP compression would still be a more robust and usable solution. P.S. You can check if your page is compressed using this online tool: Port80 Software
answered 30 Jan '11, 16:17