Hi,

I noticed that if I change an application and publish it on my webserver again, then not everybode gets the new version immediately. I often have to tell them they have to refresh the browser. I can not change the headers of my " index.html" file of my application and insert a max-age haeder of something like that. How do you handle this?

Greetings,
Ronald

Ronald wrote:

> I noticed that if I change an application and publish it on my webserver again, then not everybode gets the new version immediately. I often have to tell them they have to refresh the browser. I can not change the headers of my " index.html" file of my application and insert a max-age haeder of something like that. How do you handle this?

How are you expecting it to get refreshed? No web page is refreshed automatically when an update is uploaded - you have to either manually refresh, or something has to determine when to refresh. When the browser makes the refresh request, it will often ask the server if it has changed, and if not, no page is transferred. But that depends on the server, and I'd expect the new page to automatically be spotted and handled.

So that then leave the situation where the user is working away in your application, and the server is updated. I don't think I'd normally want any user to have their application just disappear and refresh on them - they'd lose everything they were working on unless you code it to restore (and even then it would be unfriendly).

If you did want to tell people that an update was available, you could use a call to the server to check, and then tell them, and either manually or automatically refresh. But I think I'd let the user refresh when they choose.

Or did I completely mis-understand your question?

--

Matthew Jones

"Matthew Jones" wrote:

<<How are you expecting it to get refreshed?  Or did I completely mis-understand your question?>>

I had hoped that my webserver (IIS) "sees" that html page on is new(er) and it then sends the new(er) page in response to the request of my browser. Now it seems that the webserver sends a 304 Not modified.

Ronald wrote:

> Now it seems that the webserver sends a 304 Not modified.

Well, that is indeed a problem. Which server? And I presume the file actually is modified, not stuck in transit or something.

--

Matthew Jones

Ronald,

<< I had hoped that my webserver (IIS) "sees" that html page on is new(er) and it then sends the new(er) page in response to the request of my browser. Now it seems that the webserver sends a 304 Not modified. >>

The only way that should occur is if the files *weren't* actually modified.  Did you double-check to make sure that the files actually got uploaded/deployed to the correct location properly ?

Tim Young
Elevate Software
www.elevatesoft.com