This message has been edited. Last edited by: <Kathryn Henning>,
WebFOCUS 8105m Windows, All Outputs
July 29, 2015, 03:03 AM
StuBouyer
In the WebFOCUS Admin Console you can set the Cache-Control value.
By default it is public, max-age=2592000.
Open the Admin Console and Under "Application Settings" select "Filters".
Your browser and it's version will also play a part in this. I find that IE is very greedy on keeping hold of data and cookies. Even when all pages to WebFOCUS are closed, if another IE page is open then the session cookie may not be released.
Also different browsers use different META tags to control cache.
interesting, jv... what does that quoted code do, actually?
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
August 04, 2015, 10:50 AM
Jveselka
StuBouyer
So what would we set the control to, 0?
Susannah I am not sure I found this online and I assume it is supposed to hold the compatibility settings when moving from one WF page to another.
A lot of our users are complaining that they have to keep resetting the compatibility settings each time they load our WF pages. We also have problems with the RUN button not working. You have to click tools and then compatibility mode to get it to start working again. As far as I know this seems to have helped.
The big issue is the caching......
Thanks JV
WebFOCUS 8105m Windows, All Outputs
August 04, 2015, 11:21 AM
susannah
HMMM. thanks. i'll put that code in every launch page....
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
August 04, 2015, 01:16 PM
Jveselka
I tried changing the setting and that did not help, FYI this is a IE problem for sure as I tried to load both BETA and PROD links with Firefox and all worked as it should.
I also tried using the other meta code with no luck.
Do you know where the following java script is run from? the IV_JCT=%2Fwebfocusbeta8 is what I think needs to be cleared each time. As you can see the meta code comes after it and by that time it is too late.
This should tell various Internet Explorer versions that they should not use "compatibility mode" for this HTML. The id-tags were probably initially added by WebFOCUS and then incorrectly (id attributes are supposed to be unique on a page) copied. I suspect WF is also responsible for turning this into dubious HTML by removing the attribute quotes, exposing the equals sign in the attribute value to the HTML interpreter.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :
August 12, 2015, 10:05 AM
Jveselka
This seems to be an IE (We use IE10 & IE11) issue because this process works fine in Firefox / Chrome.
I made the change Wep5622 but it didn't help.
Can anyone tell me what is generating this code. It is not in any of my HTML code but when I look at the source code it is there. To me this is what needs to be cleared but it runs before any of my code so all the META code I am putting in seems to be running to late.