Hi,
I currently manage approx 340 domains and am pretty familiar with web protocols. I am self taught so I might be wrong, but I think I have a solution.
I don't want to get to technical but first:
Links to images are harmless.
Emeded images that are stored at a different URL are harmless.
The CPF hosted images are MOSTLY harmless. When your browser reloads a page it checks to see if the images have changed by checking their modification date. If its unchanged the browser REUSES the one from its LOCAL cache. So their really is not much of a benefit for overcompressing the images such as the blue pill UBB thingy. All you are reducing is the initial download for a new user or someone that has cleared their cache.
The same holds true for the smileys.
These smileys were not downloaded three times. They were checked against the local cache. If found, the browser requests a modification date from the server. If they are the same the browser simply reuses the local cache. If the date is different or a local copy is not found, the server downloads ONE copy of that smiley. The rest of the matching smileys throughout the site are then LOCAL copies.
I have looked into this and think I have the culprit. I'll bet my Z3 that this may take care of ALL the CPFs bandwidth problems.
CPF is hosted on a microsoft IIS/5.0 server. This server has the capability to
Compress the web pages on-the-fly before it gets sent down to the browser.
Here's my browser making a request:
GET /cgi-bin/ultimatebb.cgi?ubb=get_daily HTTP/1.0
Accept: */*
Referer:
http://www.candlepowerforums.com/cgi-bin/ultimatebb.cgi?ubb=get_daily
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT)
Host:
www.candlepowerforums.com
Pragma: no-cache
Connection: keep-alive
The thing to notice is the line:
Accept-Encoding: gzip, deflate
This tells the server that the client can accept the data as a compressed stream and gives it a choice of wither gzip or deflate.
Heres the servers response:
HTTP/1.1 200 OK
Date: Wed, 19 Jun 2002 08:27:10 GMT
Server: Microsoft-IIS/5.0
Charset: ISO-8859-1
Content-Type: text/html
PLUS LOTS OF HTML
The thing to notice here is whats NOT here.
Content-Encoding: gzip
If this had been in the http header, it would have indicated that the server obeyed the compress request and that the content of the page would need to be "gunzip'ed". I would not have received 'HTML' but a stream of binary data.
This would have compressed the text content of the page by about 90%.
It's NOT being in the header tells me that the servers option to compress on the fly has NOT BEEN TURNED ON.
Please have whoever works with the CPF server read
This and then check the configuration.
I'm almost certain that this is the problem.
If I'm wrong, I apologize..
If I'm right then leave my damn smileys alone!!