This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Caching inactive due to content filtering

If I enable content filtering, the HTTP cache is disabled. Astaro promised to improve this behavior, but when?

This is a question to all folks using ASL5 in a production environment. Is it really necessary to have proxy cache running? Does it make a difference (speed) having the cache enabled? What are your experiences?

I’m running ASL4 with Surf Protection and proxy cache enabled. The company has just one Surf Protection profile (which is practicable from my point of view).
I propose to get the same running on ASL5.

https://community.sophos.com/products/unified-threat-management/astaroorg/f/68/t/60976

This thread was automatically locked due to age.

Parents

0 Kronatus over 21 years ago

I second that argument, If my company only uses one profile, why can't I benefit from both worlds of caching, and controling access?
Let the organization administrator decide how to use the product.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Kronatus over 21 years ago

I second that argument, If my company only uses one profile, why can't I benefit from both worlds of caching, and controling access?
Let the organization administrator decide how to use the product.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Gert Hansen over 21 years ago in reply to Kronatus

Hi there all,
plz stay tuned,
fix is on the way.

regards
Gert
Cancel
Vote Up 0 Vote Down

Cancel