Directly accessing the taf that is supposed to load the image doesn’t have it
loaded.
You might want to look at the server log of ideaaustralia.com.au and see if it
captures any abnormality.
.htaccess rewrite rules could also be a culprit.
And check the ImageMagick configuration. You might not have the permission to
invoke it from taf.
Btw, you might want to append a random number when you call the reload.
E.g.
$('#IMcaptcha').load('/IMcaptcha/ajaxIMcaptcha.taf?r=' + Math.random());
This is to prevent browser cache and the same image will not be reloaded when
user hit the reload button.
To share a little more, in 1 of the projects that I was involved a few years
back; the following characters were removed due to usability:
0 (zero), 1 (one), o (alphabet O), I, L (both cases), 6 (six), 9 (nine), G
(both cases)
Older folks have issue differentiating them.
-Lance
From: Wayne Irvine [mailto:wa...@byteserve.com.au]
Sent: Wednesday, 25 April, 2012 12:23 PM
To: TeraScript-Talk@terascript.com
Subject: TeraScript-Talk: Image caching
Just another interesting anomaly with my CAPTCHA routine.
This works:
http://isellit.com.au/imcaptcha/ajax.html
Click on reload and the image is refreshed without reloading the page.
This doesn't:
http://ideaaustralia.com.au/imcaptcha/ajax.html
When you click reload it makes the call to the server and creates the new image
but the browser doesn't request the new image from the server. It sticks with
it's cached version. So no reload.
The code is the same.
The working version is on a Lion Server running OSX 10.7.3, Apache 2.2.21 and
Terascript 6.1.5.
The non-working version is on OSX 10.6.8, Apache 2.2.21 and Witango 6.0.7.
Although the Apache versions are the same the httpd.conf files are wildly
different as they are installed as part of OSX. It is here that I have spent
most of my efforts so far, playing around with caching plug-ins and settings
and expire times to no avail. Essentially I want the server to cache images but
not this one. I'd be happy for it just to work like the Lion server.
Which leads me to why I am asking this question here. The major difference
between these two set ups is the version of Witango/Terascript. It is
conceivable that Witango is returning the image reference with a different
header to Terascript and causing the browser not to reload the image. Is this a
known change/bug fix between versions and should I just get around to
installing the current version on my production server as well as my
development server?
Any other input would be most welcome too.
Wayne Irvine
_____
To unsubscribe from this list, please send an email to lists...@terascript.com
with "unsubscribe terascript-talk" in the body.
----------------------------------------
To unsubscribe from this list, please send an email to lists...@terascript.com
with "unsubscribe terascript-talk" in the body.
