My new web host doesn't have mod_expires compiled into Apache and this
is problematic because the server isn't encouraging proxies and browsers
to cache images by default. The images are even being reloaded whilst
traversing the site, even though they're being served from the same
location for different pages. This would be *so* easy to circumvent with
mod_expires, but it's simply not going to happen.
I'm just looking for opinion about the viability of using PHP to serve
images, sending with them of course Cache-Control (for http compliant >=
1.1 servers) or Expiry http headers. Is this likely to slow things down
considerably during busy periods? And will an image served by a PHP Get
request (something like http://myurl/getimage.php?image1.jpg) even be
cached by proxy servers?
--
Subtext Whore
"Where there is a perpetual fast there are very few crumbs
on the floor." - Henry James, The Aspern Papers (1888)
is problematic because the server isn't encouraging proxies and browsers
to cache images by default. The images are even being reloaded whilst
traversing the site, even though they're being served from the same
location for different pages. This would be *so* easy to circumvent with
mod_expires, but it's simply not going to happen.
I'm just looking for opinion about the viability of using PHP to serve
images, sending with them of course Cache-Control (for http compliant >=
1.1 servers) or Expiry http headers. Is this likely to slow things down
considerably during busy periods? And will an image served by a PHP Get
request (something like http://myurl/getimage.php?image1.jpg) even be
cached by proxy servers?
--
Subtext Whore
"Where there is a perpetual fast there are very few crumbs
on the floor." - Henry James, The Aspern Papers (1888)