Hey, used to have the same problem, solved it by having a random string in the img calling part. eg: first have a function to generate a modest random string (I use 8 chars) then in the image calling part call it something like this: <img src='<?php echo $your_image_gets_called_here; ?>?<?php echo $the_rand_string; ?>'> as you can see above, its an over simplified version, but you can tune it as you go along...works everytime for me. Cheers, Ryan On 5/21/2005 4:04:00 AM, Richard Lynch (ceo@xxxxxxxxx) wrote: > On Thu, May 19, 2005 6:05 am, Rahul S. Johari said: > > I did actually remove the Header which declared it as a Image/PNG and > > everything seemed to work in both the browsers. > > Great. Now it works in 2 browsers, and breaks in 237. > > You MUST separate the two. > > Period. > > > Here's my situation though... I can't separate out these two files > because > > when a user is on the verification page, where the Image exists, in > case > > he > > "reloads" or "refreshes" the page, a new image should be generated and > > displayed, so that the verification code is different each time you > reach > > the verification page. If I was to keep the image code in a > different > > page, > > the verification page will pick up the same PNG image and display the > same > > security code over and over without changing it. > > So you need some kind of "secret token" buried in the HTML which you can > decode in the image and in their submit to see if they actually used > human > eyeballs to see the image. > > There are dozens of scripts out there that do this -- Perhaps you should > review them to see how they work. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 266.11.14 - Release Date: 5/20/2005 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
