Hi Jie,
Our Case ID is 207889, feel free to quote it in yours. I told them that this bug
disables the Content System for 99% of our users so I hope they're taking it
seriously. I must admit it is a relief to see others are confirming what we were
seeing!
Best wishes,
Anthony.
--
Anthony Leonard <[log in to unmask]>
System Integrator
Computing Service
University of York
Shen, Dr J. wrote:
> We have just observed same problem this morning. Accessing to an overwritten file only displays the original file. When logged in again after an hour the modified file was displayed. I have now tried again to access a modified file immediately after overwriting, the new version of file will show up only if I delete the cache file from my browser. I think this confirms your finding. What is your ticket number please? I would like to submit a case on this problem as well.
>
> Jie
>
> ********************************
> Dr Jie Shen
> Blackboard Administrator
> Computer Centre
> University of Leicester
> Leicester
> LE1 7RH
> UK
> tel 0116 252 2243
> fax 0116 252 5027
> email [log in to unmask]
> *********************************
>
> -----Original Message-----
> From: Blackboard/Courseinfo userslist
> [mailto:[log in to unmask]]On Behalf Of Anthony Leonard
> Sent: 28 September 2005 15:20
> To: [log in to unmask]
> Subject: App pack 3 Content System not refreshing.
>
>
> 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
>
|