Hi Michaël and Nigel!
Just to make things clear: DSpace does not cache, it is the browser.
DSpace only says to the browser that the old version is still valid.
(the browser first ask for the http-headers and only if the local
content is expired, request the complete page).
To force access to updated content you can refresh the whole page
(Ctrl-R: images are also reloaded) or you can add "?anything" at the end
of the URL.
Have a nice day!
Christophe
Michael White a écrit :
Hi Nigel,
You wrote:
While experimenting with groups and restricting user access to various
collections I noted that it is possible to log out the system then
attempt to access an item in a collection which is not normally
publicly
accessible. The system will indicated that the user that created the
item is logged in one instance and in another similar experiment a
user
who was made part of a group with the required access rights will then
appear as logged on thus allowing the unprivileged user access to the
item.
Has anyone encountered this before??
Not sure if you got a response to this as I've been off for a while so
doing a very high speed trawl through a couple of weeks worth of various
mailing lists . . .
Anyway, this may or may not be related, but one thing that still catches
me out occasionally is the caching of DSpace pages - we have an embargo
feature implemented that only allows admins access to embargoed items.
If I log on as Admin, access a restricted item's "Simple Metadata" page
(from where I can open the item), log out, then revisit the item display
page I find that is says that I'm still logged on (my email address
shows in the top left even though I've logged out and the link to the
item is still displayed) - however, this is just a cached version of the
page, and if I attempt to open the item, I get (correctly) taken to our
"You can't access this item but you can request it from the original
depositor" page . . .
Whenever I encounter something like this (appearing to be logged on when
I don't think I am, or vice versa), I use Ctrl-refresh (hold down the
Ctrl key whilst clicking the browser refresh) and that forces the page
to completely reload (rather than using the cached version).
As I say, may not be related to what you're experiencing, but thought
I'd mention it just in case :-)
Regards,
Mike
Michael White
eLearning Developer
Centre for eLearning Development (CeLD)
S7, The Library
University of Stirling
Stirling SCOTLAND
FK9 4LA
Email: [EMAIL PROTECTED]
Tel: +44 (0) 1786 466877
Fax: +44 (0) 1786 466880
http://www.is.stir.ac.uk/celd/ <http://www.is.stir.ac.uk/celd/>
begin:vcard
fn:Christophe Dupriez
n:Dupriez;Christophe
org:DESTIN inc. SSEB
adr;quoted-printable:;;rue des Palais 44, bo=C3=AEte 1;Bruxelles;;B-1030;Belgique
email;internet:[EMAIL PROTECTED]
title:Informaticien
tel;work:+32/2/216.66.15
tel;fax:+32/2/242.97.25
tel;cell:+32/475.77.62.11
note;quoted-printable:D=C3=A9veloppement de Syst=C3=A8mes de Traitement de l'Information
x-mozilla-html:TRUE
url:http://www.destin.be
version:2.1
end:vcard
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
