I have a root htaccess file with:
ExpiresDefault "access plus 0 seconds"
ExpiresByType image/jpeg "access plus 2 weeks"
Lets say I have a clonable template with an 'image' and associated 'thumbnail' editable region. I upload the image. The 'image' is initially requested as: 'image.jpg' and the 2 week expires is sent with it. I hit save on the cloned page. The page reloads, and the 'thumbnail' is requested as: 'image-200x100.jpg' and the 2 week expires is also again sent with it. At this stage even if the 'image' file has been resized, my browser will continue to use the original cached 'image.jpg' as expected. Similarly, for the 'thumbnail' file after selecting a different 'crop position', my browser will continue to use the original cached 'image-200x100.jpg' as expected after saving the cloned page. On thumbnail recreation, I can see that couch utilizes a 'rand' querystring to bust any present cache-control. However this will as expected not effect the non-querystring version.
I know a simple refresh will result in the updated image and thumbnail files being sent, but I can't expect my client knowing when to do that. Without turning off expires for my '/uploads/image/' folder, can I get around this? Is there a way I could apply "access plus 0 seconds" or a redirect to a random querystring'ed version based on the referrer being from my couch directory? Hopefully I am missing a simple solution.
Oh... and Google's reCAPTCHA: http://www.google.com/recaptcha
. It would be nice to be able to use that, as I am reluctant to use couch's captcha partially because it reveals the location of the couch directory through the captcha image.
** Sorry, accidentally posted this in the wrong section. You can move it if you like.