For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

smp_86112's avatar
smp_86112
Icon for Cirrostratus rankCirrostratus
Jan 09, 2009

Processing Efficiency of multiple HTTP Class Profiles

All of our HTTP applications are deployed with a standard page that is used to determine whether the app is considered up or down. Let's say the path to the page is /status/status.html.     ...
app sec
BIG-IP Access Policy Manager (APM)
security
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Jan 12, 2009
I don't think there is any significant difference between having multiple HTTP classes. However, if each of the HTTP classes has app security enabled then there might be some overhead in having a lot of web applications and their corresponding policies. I don't think it would be a big difference though. Does anyone else have thoughts on this?

 

 

If you think the status and auth portions would require changes, and those changes would need to be replicated across all of the apps, it might be easier to administer if you break out the status and auth portions of the app. On the other hand, if you think it would be harder to administer more policies, then you could combine them. Again, I think it's a matter of which methodology is easier to maintain. I don't think the difference in performance would be significant.

 

 

Aaron
Related Content