markus, I found a flaw in your implimentation of gzip html compression on your page server. While it might seem trivial, it actually could be costing you some serious bandwidth so I wanted to alert you to it. Apparently pages are only gzipped on your site if a http 1.1 request is made, despite the correct headers/responses being sent to indicate gzip support when a http 1.0 connection is made. This is different than the typical compression response by IIS, mod_gzip (apache 1.3) and mod_deflate (apache 2.0). While modern browsers don't use http 1.0 anymore, most bots do use it and most support gzip to save your bandwidth, which you aren't taking advantage of. Since bots use far more bandwidth than human visitors, this adds up every month. If you were using php I could suggest to you in a heartbeat how to fix this, but on your asp.net I would have no clue. So I hope it's just as easy. I discovered this by accident while testing a new page/site analyzer I am writing and was trying to come up with interesting pages to analyze.
| 
