Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

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

by pstone (Initiate)
on Jan 15, 2009 at 16:48 UTC ( #736584=note: print w/replies, xml ) Need Help??


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

/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 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
    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)

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' +, );
      Awesome - Thanks everyone! Back to da sleeves!
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.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://736584]
help
Chatterbox?
[Lady_Aleena]: Why XP?
[Discipulus]: it is for my father: it is impossible to tell him to learn a newer OS
[Lady_Aleena]: To tell him or teach him?
Discipulus anyway xp is still the best lowend game machine
[Discipulus]: both: everyting must be identical in the new v-machine
[Lady_Aleena]: So putting a nice DE or WM up on a Linux machine is not an option?
[Discipulus]: i need some converter to have directly an OVF format directly: at the moment i'm trying with vmware converter standalone
[Lady_Aleena]: I don't know what to tell you. I can barely get my Linux machine to do things I want.
[Discipulus]: if DE or WM means desktop env and win manager.. no, not an option
[Lady_Aleena]: That's what they mean, at least to me. 8)

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (7)
As of 2017-05-22 18:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?