HTTP Optimization on Non-Standard Port

Unanswered Question
Jan 5th, 2010

I was wondering if anyone else has noticed something similar to what I am seeing.

We have a WAAS setup running 4.1.5a. It has been working very smoothly but I've noticed something odd

regarding HTTP optimization. All users trying to access the Internet must use a proxy-server on HTTP port 9090.

The WAAS does a good initial job of optimization on small amounts of traffic (under 2MB's, not exact just an observation)

the optimization can be upwards of 80-90%. However, if a large file transfer is done the amount of optimization drops to almost

nothing and at times it is slightly negative.

However, there are internal servers users access on HTTP port 80 and the optimization on all the traffic averages around 70-90%.

Would anyone have an idea as to why this might be?


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Zach Seils Tue, 01/05/2010 - 14:37

Hi James,

I would expect overall lower compression ratios for content coming from the Internet, since the content types are more likely to vary (YouTube, etc.) versus intenally hosted content.

Can you post a copy of the 'sh stat app Web' so I can look at the statistics?



JAMES HAYNES Wed, 01/06/2010 - 08:49

Hi Zach,

That's actually a very plausible reason. I hadn't thought about streaming video.

I am away but will post the output of the command you suggested when I get back.




This Discussion