I'm trying to help a customer on a (I believe) caching issue using
BorderManager.
The short story is they (customers offices) are having unreliable
responses
running our web application. They commented they could cure the issue
for
'a few days' by clearing the network cache (BorderManager).
So I suggested adding a domain exclusion (no cache) by using
BorderManagers
'Cachable Object Control Parameters'. They did this. Everything's fine
for a
few days. Bam. Sporadic problems return.
If they clear the network cache and cure the problem again I feel they
must
still be caching the domain.
So, finally, the question:
Are their any known issues/tricks/experienced user tips that might
help? I
am limited by the fact that I'm not a Novell/BorderManager admin, so I
can't
speak in BorderManager specific terms.
For example, are configuration changes dynamic, or is it necessary torestart the service after making changes, a la kill -HUP for Unix
daemons?
For reference, I test the app in house with a caching server (Squid)
without
problems. Also, none of our other customers have similar problems for
me to
compare with.
Any insight appreciated. We really want to help them use our
application
satisfactorily.