Build Your Own Arcade Controls Forum

Main => Forum/Website Discussion => Topic started by: richms on July 11, 2005, 01:38:19 am

Title: Cacheability of site images
Post by: richms on July 11, 2005, 01:38:19 am
Its quite annoying that the images on the forum site are not cachable. Means that every time I go to a page, I have to sit while all the images load - especially bad on a page with loads of posts for a project log.

I realise that the site cant do anything with off site hosted images, but the ones that are inline with the forum should be something that the php can just spit out an expiry header before the image content.

Able to be looked at please? Would also save the site considerable bandwidth.
Title: Re: Cacheability of site images
Post by: sirwoogie on July 11, 2005, 04:12:18 pm
Bandwidth isn't really a problem, but I'll look at the expiration. I wasn't aware it was setting them on all items, rather it should just do the text.  Let me see what I can do.
Title: Re: Cacheability of site images
Post by: RayB on July 12, 2005, 03:06:54 pm
There's not much they can do about avatars that are linked from outside of this site...

Plus isn't the caching more of a browser side setting?
Title: Re: Cacheability of site images
Post by: richms on July 13, 2005, 05:17:38 am
The browser will only obay what the server sends. If the server doesnt send an explicit expires time then the browser is left to guess, and it seems firefox/mozilla are more likly to  - same for proxys along the way.

Im stuck on a 256k internet connection here because its the only one available in NZ without rediciously low transfer quotas before the speed plummits to an un-usable 64k, as the latency is high coming across half the globe even the faster connections dont really speed up page load times from forums like this.

Avatars are dealt with by turning them off :) its inlined images that are the killer like in the project threads
Title: Re: Cacheability of site images
Post by: sirwoogie on July 13, 2005, 10:52:12 am
Unfortunately, this is a catch-22. If I set the control to "private" many people will start having trouble with various areas of the site. It's simply a way to ensure that content stays correct when a user views a page. Some browsers will even cache the content if told not to by the server. Sorry, the only other solution I could suggest to you is filter your content through a local proxy to get some of the caching benefits.