Has anyone had problems with a client’s network proxy caching in xPages?
What I’m seeing with a client that has caching on their network is the xPage AJAX calls are getting cached on their server. The huge problem with this is the caches are not user specific. So data is being sent back that was for another user.
This caching is also crashing the Domino server. My assumption is Domino is getting totally confused by the requests that are actually making it to the server because the data being sent is not what it was expecting.
I’m working on getting the client to bypass the proxy caching for our server IP.
But I still have 2 key issues/questions here:
1 - Why is the server crashing? This is unacceptable to actually completely take down the server for something like this - it should be able to handle this without crashing.
2 - Is there any way we can bypass this server caching? I know proxy caching is used in lots of company networks (including hotels). I always have appended a &rnd=[date/time] to any ajax calls I’ve used before to work around this. But I can not do that for xPage requests. But I think that’s the only way to ensure a network is not caching a call.
Any help / guidance will be appreciated!
- Barry McGovern
PS: I will be submitting a support ticket on this - but I haven’t done one of those in years - so it may take me a while to figure out how that’s done.
PSS: This caching is the cause of yesterdays request - it can appear to switch users because the cached response may contain another username in it: