Steve, paranoia is set to no. The issue that I see is that that the Refresh option is not coming across in the page info. I know routers2 controls this when you are looking at the main page but for some reason it is not being passed across. I have Cricket running on the same server ( the app I am trying to replace with MRTG ) and it passes the Refresh option to both IE and Firefox without any issues. I am not able to get off Cricket until this issue is resolved..... Hopefully I am not asking the impossible.
-Patrick ----------------------------------- Steve Shipway wrote: > Unless you have the 'paranoia=yes' option set, then if you look at the graph > page HTML you will find at the end a comment block detailing the refresh and > expiry information set for that frame. > Page refresh should always be set for the graph frame, if not showing and > archived graph. > Your problem may instead be due to your web browser - sometimes, IE will > cache web pages even when they are set to 'no cache' and can ignore expiry > times. Also, if your web browser clock is out of synch with the web server > clock you can get this problem. > 1. Check your web browser and web server clocks are in synch to the second > 2. Check you have 'check for newer versions' set to 'automatically' in your > IE cache settings. > > Steve > > ________________________________________ > From: Patrick Topping [[email protected]] > Sent: Saturday, 7 November 2009 9:37 a.m. > To: Steve Shipway > Cc: [email protected] > Subject: Re: [mrtg] MRTG and web page refresh > > Steve, > > We are linking over the page via a 'naked' graph page. I have the > following enabled in the router2.conf file: > > # set to +2d if you want all autorefresh pages to work > auth-expire = +2d > > # Normally, graphs refresh automatically as soon as they become out of date. > # This is about every 5 mins for daily graphs. You may wish to make the > # minimum refresh time larger to prevent too-frequent updates > # integer in SECONDS, default is 0 > minrefreshtime = 300 > > Am I missing anything here? > > -Patrick > > ------------------------------- > > > > Steve Shipway wrote: > >> The routers2 autorefresh depends very much on how the page is generated. >> How are you linking in to Routers2 from the external pages? If it is by >> using embedded images, or a 'naked' graph page (no header or menu) then the >> autorefresh is either not possible or is disabled. If you are using the >> URLs generated by clicking the 'bookmark' button, however, the generated >> HTML should autorefresh at the appropriate frequency (the refresh code is >> hidden in the HTTP headers of the graph pane). Otherwise, you'll need to >> code the HTML to refresh yourself. >> Another thing to note is that your web server must accept the refresh >> headers from the CGI but that shouldnt be an issue with most web servers. >> >> Steve >> >> ________________________________________ >> From: [email protected] [[email protected]] On >> Behalf Of Patrick Topping [[email protected]] >> Sent: Friday, 6 November 2009 3:54 p.m. >> To: [email protected] >> Subject: [mrtg] MRTG and web page refresh >> >> I am using routers2 as my primary front end to MRTG. I have some other >> apps that use the links inside MRTG to populate web pages for the NOC >> and other departmental views. The issue I am having is these web pages >> are not refreshing themselves automatically. I did not add the Refresh >> option into the cfg files because the default is 300 seconds. I have >> added this option and set the refresh rate to be 300 seconds but no >> change. Anyone have any idea what could be causing the issue? Any help >> would be greatly appreciated. >> >> Thanks in advance. >> >> -Patrick >> >> >> >> _______________________________________________ >> mrtg mailing list >> [email protected] >> https://lists.oetiker.ch/cgi-bin/listinfo/mrtg >> >> >> >> > > > _______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
