Ticket #64 (closed Issue: worksforme)

Opened 1 year ago

Last modified 5 months ago

Browser caching publish response?

Reported by: lois Assigned to: Garth
Priority: Low Milestone:
Component: Admin Webapp Version: 2.0
Severity: Keywords:
Cc:

Description

I think this is just a browser caching thing, but it is something to be aware of. This happens when I have published an indicator, and I publish it again in the same brower session. I get the successful publish message, but the new content does not go out to the View application. I tried using a different browser (Firefox, vs. I.E.) to VIEW the indicator, and the content really wasn't there. So I don't believe it is merely an issue with caching the indicator page.

I close and reopen my browser I can publish the indicator, get the successful publish reponse, AND view the content via the View application or pull down the xml file.

Change History

09/04/10 20:20:11 changed by lois

  • component changed from view to admin.

10/12/10 15:21:11 changed by lois

  • priority changed from trivial to minor.

12/15/10 14:14:59 changed by lois

  • milestone changed from IBIS-PH Admin-2 to Ideas for Version 2 Enhancements That Are Not on the Current ToDo List.

06/20/11 13:33:45 changed by garth

  • status changed from new to closed.
  • resolution set to worksforme.

Publish is only requested from the user's browser. The actual publish takes place between the apps - not the browser. The message "could" be cached and a proxy "could" be in the way when the admin and view apps are communicating. More info is needed.

09/14/11 11:32:37 changed by

  • milestone changed.

Milestone Parking Lot deleted