nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

browser cache

EricGardecki

It seems like I often have to clear my browser's cache after updating some things with my web app or else the changes do not show. Clearing the REST cache doesn't take care of everything. I think the average user would not think to clear their cache let alone even know how and they would not see changes/fixes. Is there a way to force it on load somehow? If not, Any ideas on how to get people to understand that it may be necessary? I doubt that a snippet in a help page would be enough....plus when would they even know that a change has been made and they need to clear it?

thanks!

Encontre mais publicações marcadas com

Accepted answers

MattiasEkstr√∂m

sorry, your code above was a mix of what it should be in the index.template.html and the index.html.
In the index.html it should be:

swfobject.embedSWF(              "index.swf?ts=" + new Date().getTime(), "flashContent",                 "100%", "100%",                 swfVersionStr, xiSwfUrlStr,                 flashvars, params, attributes);

All comments

JasonStanton__GISP

One (likely) big difference is that everything on my server runs through SSL.

EricGardecki

I am using Robert's TOC as well. I'm starting to think there is a conflict there for 3.1 but I don't know why it only happens for one of my users on this end.

Maybe i'll try to remove some of the edited code and see if it has an effect. It is difficult for me to test though as the machine with the issue here is in use.

If I'm able to figure anything out I will let you know.

JasonStanton__GISP

It was working fine using unedited ConfigManager and Robert's TOC v3.1. Once I changed to the edited version it fails.

EricGardecki

Does this same thing happen while using an unedited ConfigManager?
Are you using the original TOC or Robert's custom?

JasonStanton__GISP

Thanks for the file but that didn't help me. Same thing with all three browsers.

EricGardecki

This is what I am using. I have only had it live for a few days but all seems well other than that one user I mentioned.

Hope it helps.

FYI I haven't used Firefox at all for my application so I can't comment on that. I use both IE and Chrome, as do our local users.

EDIT: For future reference, this is for version 3.1

ConfigManager.zip

2.2 Output.PNG

JasonStanton__GISP

Thank you so much for the quick reply. I am having the issue in Firefox. I would love to try your version and see if it helps, thanks!

EricGardecki

First I'd just like to say that this is a huge PITA to deal with every time I change versions (i just reverted back to 3.1 actually), especially since that ConfigManager changes slightly apparently and I'm not sure if I'm editing it correctly based on the file Robert posted above.....so I really wish that this would just be incorporated in the the viewer by ESRI as it seems like an absolute necessity to me.

I'm not sure if the issue you are seeing is what I've just noticed myself. One of my users is having an issue where (when using IE only) the widgets do not load as they seem to hang as they wait for the TOC to load. IF this is the same issue as you are experiencing, note that this is only (afaik) happening to this one user on my end so I believe it is an issue with IE or flash player on that machine. Check to see if the same thing happens on another browser or machine.

If that is not the case for you, I can offer you my edited ConfigManager.as for 3.1 to add in your project and see if that helps.

JasonStanton__GISP

I incorporated the 3.0 files into my 3.1 application. It prevents the caching but layers are not showing up in my TOC widget, which causes issues opening all other widgets. Does anyone have any thoughts?

jamesdiaz

James,

A compiled version would really mean a whole Flex Viewer compiled project and I don't get involved in doing that. This is something that if you want this capability then you will need to be using the source code (not the compiled viewer).

Robert,
thanks for your reply, I will take the same you provided on post #22 but for 3.1.

thanks

RobertScheitlin__GISP

James,

A compiled version would really mean a whole Flex Viewer compiled project and I don't get involved in doing that. This is something that if you want this capability then you will need to be using the source code (not the compiled viewer).

jamesdiaz

anyone????
thanks

jamesdiaz

Robert, would you happen to have a 3.1 compiled version?

PetraStrbenac

Robert, thank you very much for your effort! I replaced the default files with the ones you prepared, compiled the app and everything is working fine now, with no client-side caching

.
Petra

RobertScheitlin__GISP

Petra,

Sure here is all the code changes in these posts consolidated. There are three file that need changing. All changes are commented in the source files.

FV3.0-src.zip

layout coordinates.py.zip

PetraStrbenac

What about Flex Viewer version 3.0?

I tried applying time-stamps to ConfigManager.as and I also tried making time-stamp changes to index.html (swfobject.embedSWF) but in case of ConfigManager.as changes, I got error #2124 (Loaded file is an unknown type.). In case of index.html modification, I got blank page.
Since I could only find modified ConfigManager.as and other suggestions for previous versions of Flex (2.3, 2.5) I was (at least I think I was) careful to apply time-stamp changes correctly. I also had to change Date().getTime to Date().time, since getTime was not recognized by Flash Builder.
In addition I tried adding the following meta-tags to index.html but non of it helped:
<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Expires" CONTENT="-1">
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">.

Can anyone please help me find the solution for disabling client-side caching for Flex Viewer 3.0 application? It is really annoying that I have to clear the cache in order to reflect even minor changes to my application. Even bigger problem is that I have to periodically make changes to the application so returning users experience problems with loading the new version of the application (since the previous version is already cached on their side).

Any help or suggestion would be greatly appreciated!

Petra

DanielJohns

Okay, so I've modified just the ConfigManger.as. Completed the 'Export Build Release' and moved it to the production server.

I enter the url http://server/flex and nothing changes (still pulling from cache). Should I be expecting to see server/flex/index.swf?...

Update: Well, I think it's finally working.

I took the zip from http://forums.arcgis.com/threads/57121-browser-cache?p=197488&viewfull=1#post197488
and used the ConfigManager.as, the only difference from ours was the double ;; on a couple of lines (I used one).

I also added swfobject.embedSWF(
                "${swf}.swf?ts=" + new Date().getTime(), "flashContent",
                "${width}", "${height}",
                swfVersionStr, xiSwfUrlStr,
                flashvars, params, attributes);

back to the Index.html and it loaded a fresh page 😄

Now for more testing. Thank you!

DanielJohns

I'm actually doing that right now. I found another forum post that mentions it.

http://forums.arcgis.com/threads/16664-Preventing-client-side-caching-of-the-Flex-Viewer?p=105311&viewfull=1#post105311

I have 2.5 (Robert provided the one for 2.3.1) so I have to search and replace, but it this works I will reply.

Thank you

EricGardecki

Have you applied the time stamps to the multiple lines in the ConfigManager.as?

DanielJohns

Hi, I'm using 2.5 and was trying to achieve the same thing (disable the swf caching). I've attempted the recommendations above, but it's still loading the old version from cache (using IE9).

I've tried the MapManager.mxml mod and also the Index-template mod (also verified the build) with no success.

I'm using the eSearch tool as well as a splash page (not sure if that would make a difference).

my Index-template.html has the following mod.

swfobject.embedSWF(
             "index.swf?ts=" + new Date().getTime(), "flashContent",
                "100%", "100%",
                swfVersionStr, xiSwfUrlStr,
                flashvars, params, attributes);

Flash also ignored the following (for those who may come across other post).

<meta http-equiv="Cache-control" content="no-cache" />
<meta http-equiv="Cache-control" content="no-store" />
<meta http-equiv="Cache-control" content="must-revalidate" />
<meta http-equiv="Cache-control" content="max-age=-1" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Pragma" content="no-store" />
<meta http-equiv="Expires" content="-1" />

Thank you for any recommendations to resolve the issue 😉

Daniel

EricGardecki

that did it. thanks again.

MattiasEkstr√∂m

sorry, your code above was a mix of what it should be in the index.template.html and the index.html.
In the index.html it should be:

swfobject.embedSWF(              "index.swf?ts=" + new Date().getTime(), "flashContent",                 "100%", "100%",                 swfVersionStr, xiSwfUrlStr,                 flashvars, params, attributes);

EricGardecki

ok I made that change in the MapManager.mxml and it seems to work perfectly. Thanks!

As for the index.html, when I make that change the application doesn't load. I get a message about it requiring flash 10.2. I am up-to-date. Are you sure my code above is exactly right?

MattiasEkstr√∂m

Eric, yes that change will make sure that the main application index.swf is not loaded from the browser cache.
Due to some datatype problems with the PopUpConfig URLs in ConfigManager it is easier to do that fix in the MapManager.mxml
Look for the line:

var popUpConfigURL:String = arrLayerPopUp.popUpConfig;

It should be around line nr 1017, and replace it with:

var popUpConfigURL:String = String(arrLayerPopUp.popUpConfig) + "?ts=" + new Date().getTime();

That should make sure that PopUpConfigs doesn't load from browser cache...

EricGardecki

I haven't done anything to the index.html so I revisited that thread. So I should change this:

swfobject.embedSWF(
                "index.swf", "flashContent",
                "100%", "100%",
                swfVersionStr, xiSwfUrlStr,
                flashvars, params, attributes);

to this?

swfobject.embedSWF(
                "${swf}.swf?ts=" + new Date().getTime(),
                "100%", "100%",
                swfVersionStr, xiSwfUrlStr,
                flashvars, params, attributes);

as for the new .swz files, apparently they are required to go along with the new index.swf because it didn't work without them.

I did notice that this cache fix did not work on the "MySplash" widget, but maybe the change above will take care of that.

thanks

MattiasEkstr√∂m

Eric, I reacently noticed that this fix doesn't apply to the PopUpConfig-files too. It was a little bit more tricky to fix than I first thought, I will try to solve it and post back here when/if I'm able to solve it...
As it is now it applies to config-files, both main-configs and widget configs and all widget swf files. For the index.swf I think you have to add a timestamp to the index.html file if you haven't already done that.

Concerning the .swz-files I don't think there is any differens between them so you can just take the index.swf. But I'm not 100% sure...

EricGardecki

My flash players are all up to date already so there was nothing to update. I tried it in multiple browsers and multiple computers as well.

As for the index.html. I was just trying to follow the developer help page you linked to. It suggested running the index.mxml within FB, prior to compiling, to be sure it's working. That's when I got that error.

That being said, I decided to try again and ignore that error. I replaced the ConfigManager.as in the project with yours that was posted above, compiled, and tested it out. It is loading just fine now. I then tried a couple quick changes to test out the cache thing. Changes to a widget happened without having to clear the browser cache, however, when I changed something in a popup config I could not see the change without clearing the browser cache. Apparently there are some limitations to what this fix applies to. Do you have a handle on what those limitations may be? So far it seems that it applies to widgets and changes to the config.xml....which is definitely great...but what does it not apply to and why? And can this be changed?

Thanks for your help. I'm glad to have this working.

Oh... the compile creates several *.swz files along with the index.swf that apparently match the version of FB. Must I use the versions I created or can i just take the index.swf alone out and add to my viewer?

MattiasEkstr√∂m

Eric, the problem with a blank white screen and no errors I've had before. I could solve that by installing a new version of flash player. I don't know what was wrong, the version I had was supposed to be working. Try updating your flash player and see that changes anything.
The index.html is supposed to be created when building the project, it's based on the index.template.html in the html-template folder.

EricGardecki

Mattias, thanks for the response.

I tried your index.swf and get the same result as the one I compiled. The url to the viewer appears to find something, as in no browser errors, but I get a blank white screen. Flash loads but no viewer. I get no errors anywhere. This same testing application works just fine with the esri compiled version of the file.

I then again loaded the source in FB and simply tried to run it before doing anything (as in your link) and I get an error saying it can't find index.html. All I did was import the project and add the sdk as is and there are files missing??

I'm thoroughly frustrated as to why either thing isn't working and don't know what else to do. Any ideas? Thanks

jessebelcher

mattias_j,

Thanks for the reply.. i am trying to get the basics down before i jump into the non compiled Api version..

I have replaced my index.swf with the one from your post.. i am testing it now. Good news is everything still works as it did before. Not sure about the cache as of yet but i will let you know.

Thank you for you help on this.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.