• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Novell BorderManager Caching Problem

W

WobbleWobble

Diamond Member
I'm having a problem with BorderManager pushing out the old version of a page until the next day.

I'll have a page that has the date/time outputted using ColdFusion and replace that page with a page with some real content on it.

Bypassing the proxy, I can see the new page with the content on it.

Using the proxy, I'll see the date/time page (with an old date/time) when I first enter the page, then I have to refresh the browser to see the new version of the page. Close the browser and go to that page again, I'll get the old version then I have to refresh to see the new one.

This will happen to any computer using the proxy even if they haven't visited the page before. This leads me to believe that it's not a local browser caching problem and because I see the new updated page when I bypass the proxy, it's not a web server issue.

Using the proxy, I will get the new page the next morning.

This is using BorderManager 3.7.

I've used meta tags to try and tell the proxy not to cache the pages, but it seems to ignores it. The meta tags I've tried using are:
<META http-equiv="CACHE-CONTROL" content="NO-CACHE, NO-STORE, MUST-REVALIDATE">
<META http-equiv="PRAGMA" content="NO-CACHE">
<META http-equiv="expires" content="Tue, 20 Aug 1996 14:25:27 GMT">

So, does any have any suggestions? However, I'm not the network administrator. I'm an web developer who has to work behind the proxy and I have to make sure that the users who are also behind the proxy server see the most recently updated pages.
 
Originally posted by: WobbleWobble
I'm having a problem with BorderManager pushing out the old version of a page until the next day. I'll have a page that has the date/time outputted using ColdFusion and replace that page with a page with some real content on it. Bypassing the proxy, I can see the new page with the content on it. Using the proxy, I'll see the date/time page (with an old date/time) when I first enter the page, then I have to refresh the browser to see the new version of the page. Close the browser and go to that page again, I'll get the old version then I have to refresh to see the new one. This will happen to any computer using the proxy even if they haven't visited the page before. This leads me to believe that it's not a local browser caching problem and because I see the new updated page when I bypass the proxy, it's not a web server issue. Using the proxy, I will get the new page the next morning. This is using BorderManager 3.7. I've used meta tags to try and tell the proxy not to cache the pages, but it seems to ignores it. The meta tags I've tried using are:
<META http-equiv=CACHE-CONTROL content="NO-CACHE, NO-STORE, MUST-REVALIDATE">
<META http-equiv=PRAGMA content=NO-CACHE>
<META http-equiv=expires content="Tue, 20 Aug 1996 14:25:27 GMT">So, does any have any suggestions? However, I'm not the network administrator. I'm an web developer who has to work behind the proxy and I have to make sure that the users who are also behind the proxy server see the most recently updated pages.
Click to expand...

Are you using BorderManager or iChain?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top