|
I think you may be SOL.
I did a quick look at program they're using and from a network admin prespective; it rocks and will definately handle a lot of bandwidth issues.
http://www.packeteer.com/products/packetshaper/#1
| quote: |
PacketShaper is an application traffic and bandwidth management system that delivers predictable, efficient performance for applications running over the WAN and Internet. The combination of its layer 7 classification, analysis, control, and reporting capabilities enables network administrators to keep critical traffic moving at an appropriate pace through bandwidth bottlenecks and prevents any single type of traffic from monopolizing the link.
|
So to answer your question, HTTP is part of the 'Application Layer' (Layer 7) in which this program is specifically choking.
| quote: |
With PacketShaper, you can classify traffic by application, service,
protocol, port number, URL or wildcard (for Web traffic), user
speed, host name, precedence bits, and IP or MAC address.
|
source
Basically they got you by the short and curlies and the days of suckin' school bandwidth are over...
___________________
"...End? No, the journey doesn't end here. Death is just another path...one that we all must take.
The grey rain-curtain of this world rolls back, and all change to silver glass...and then you see it...
...white shores...and beyond...the far green country under a swift sunrise."
|