Hi all,
We've hit a serious caching problem with the App pack 3 Content System (version
2.3), and now Blackboard have now replicated it on their own servers.
Basically if a user opens any file in the content system, then modifies it, and
then opens it again, the old version will always be shown. Hitting refresh or
even logging out and back in again doesn't help. Only if the browser cache is
explicitly deleted will the new version be shown. This occurs no matter what
browser or platform is used because the error is actually with the server.
Using an HTTP sniffer shows the browser's GET request from the content system
correctly includes an "if-modified-since" header with the date of it's cached
version. However the Blackboard server wrongly responds with a "HTTP/1.0 304 Not
Modified" even when the file has indeed been modified since that date. The
browser accordingly uses it's cached version.
Blackboard's workaround is to "tell the users to set their cache to 0 Mb".
They're escalating it to their developers.
If anyone else can see this in their own systems I'd be grateful to know about
it. We're using Solaris 9, Oracle 9.0.2.
Best wishes,
Anthony Leonard.
--
Anthony Leonard <[log in to unmask]>
System Integrator
Computing Service
University of York
|