Re^2: How to wait until GD Image it written, then continue

/grumble

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

Comment on Re^2: How to wait until GD Image it written, then continue

Replies are listed 'Best First'.
Re^3: How to wait until GD Image it written, then continue by shmem (Chancellor) on Jan 15, 2009 at 17:00 UTC
The following works for me: `my $q = CGI->new; print $q->header( -expires => '0', -pragma => 'no-cache', -cache_control => 'no-store, no-cache, max-age=0, must-revalidate' +, );` [download]	[reply] [d/l]
Re^4: How to wait until GD Image it written, then continue by pstone (Initiate) on Jan 15, 2009 at 18:22 UTC
Awesome - Thanks everyone! Back to da sleeves!	[reply]
Re^3: How to wait until GD Image it written, then continue by andye (Curate) on Jan 15, 2009 at 16:53 UTC
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? these HTTP header values may be relevant `'Pragma' => 'no-cache' 'Cache-Control' => 'no-cache' 'Expires' => 0` [download] another method is to make sure the URL is different each time (e.g. by appending a GET parameter showing the current datetime). hth! a. 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)	[reply] [d/l]
Re^3: How to wait until GD Image it written, then continue by mr_mischief (Monsignor) on Jan 15, 2009 at 16:54 UTC
Take a look in RFC 2616 for the 'cache-control' HTTP header.	[reply]