Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 242
  • Last Modified:

Possible to require browser to retrieve fresh copy of page?

I'm building my first truly complex ASP.NET / VB.NET / JavaScript / jQuery web form.  And, to be candid, I've had to work out a few bugs after going into production.  Fortunately, the form lives on an IIS server with a private IP, so it isn't too hard to fire off an email to my users saying, "I've updated the web form.  Please load the page and press F5."  Here's the kicker, many of them forget to press F5. Subsequently, my phone has been ringing a lot.  Is there a way to configure the web form that tells my user's browsers (mostly IE 8 and Firefox 3.5 and 3.6) to grab fresh copies of the HTML, CSS, and JS files every single time the page loads?  If there is, I'd turn this feature on for a period of a week or so, then turn it off after I work out the bugs.
0
jdana
Asked:
jdana
3 Solutions
 
Shaun KlineLead Software EngineerCommented:
In IIS, you can change how pages are cached by the client. In the properties for your website, go to the HTTP Headers tab and enable content expiration. The proper setting would be "Expire immediately".
0
 
mkobrinCommented:
You can also prevent caching by adding the following in the heading:

<meta http-equiv="pragma" content="no-cache" />

but that will reload this page every time.

Will still require a refresh from the clients side once after the change is uploaded.

When you are fined testing you can remove the line and the next time the user load the page it will cache again
0
 
mattisflonesCommented:
IIS, Site, HTTP Headers, "Enable content expiration"->"Expire immediately".
That combined with a timer that triggers a update should do the trick..


But, my real answer is: Dont dev that way! Its bad!


0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
jdanaAuthor Commented:
mattisflones,

You stated, "But, my real answer is: Dont dev that way! Its bad!"  Okay, sounds reasonable, what would you suggest as an alternative?

J
0
 
mattisflonesCommented:
Easy.. Dev, test, fix, test (Loop until satisfied).

Then publish.
0
 
jdanaAuthor Commented:
Thanks!
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now