rateclass on HTTP request uri?

Hmm...

 

 

Each user is a little difficult. When I looked at doing this, I discovered that rate classes aren't really designed to limit individual connections, but more to limiting to a pool...

 

 

What that means is if you simply assign everyone to the same rateclass, they SHARE the bandwidth limitations. The only way I found to do it was to have a rateclass per user. Which worked for the app I was implementing at the time (A small number of relatively static users), but may not work for you.

 

 

I believe that v11 still works the same way... (I just had a quick peak at the docs in the TMOS concepts manual).

 

 

H