in reply to
Re: How to wait until GD Image it written, then continue
in thread How to wait until GD Image it written, then continue
WHY Firefox WHY? You moved the headstones but you left the bodies! WHY!?
Well.. heh... that was it - I was going crazy - local cache issue...
Is there some spooky content command or something to tell a user's browser to not cache files or something like that so this doesn't crop up for other users?
The issue is that the # of files is set to 30 then it wraps and sure enough, once a user looks at 30 sleeves, this starts to happen. :P
these HTTP header values may be relevant
'Pragma' => 'no-cache'
'Cache-Control' => 'no-cache'
'Expires' => 0
update: don't forget, the user's browser isn't the only place that caching can occur. it can happen at your end, at the user's end, or anywhere in between (e.g. reverse caching proxy at the ISP)
The following works for me:
my $q = CGI->new;
-expires => '0',
-pragma => 'no-cache',
-cache_control => 'no-store, no-cache, max-age=0, must-revalidate'
Priority 1, Priority 2, Priority 3
Priority 1, Priority 0, Priority -1
Urgent, important, favour
Data loss, bug, enhancement
Out of scope, out of budget, out of line
Family, friends, work
Impossible, inconceivable, implemented
Results (89 votes),