|Last update Jan 21, 2020|
ProblemIf you are not seeing any pictures at all on my site the reason is simple; however, the explanation is complicated.
ReasonYour firewall is replacing the html header referring page field with an advertisement for itself, or you are viewing my pages using the Google translate utility. (My friend, webmaster, is working on a solution for the translate problem)
Another important component in the html header is the referring page field which contains the address of the page you were viewing which requested this file. If you clicked a link which sent you here, that page's address is included. For an image, the referring page would be the page the image is shown on.
This is what your computer is reporting as your referring page, which would be the page you just came from.
The referring page data is very useful in analyzing the traffic to my website. For example if you clicked a link which pointed to a missing page (Error 404, file not found) I can find the referring page with the defective link and fix it.
Bandwidth or more accurately, data transfer
While bandwidth theft is not illegal, it is generally considered unethical. Imagine hundreds of people using your cell phone without your permission. My webmaster recently helped a friend revamp his site. After analyzing his log files, he realized his bandwidth theft was 70 times the data transfer his actual site was consuming, and that was from only 2 pictures being embedded on numerous MySpace blogs. Luckily his site was very small and the total data transfer was still below his allotment. HorseHints is growing steadily. I cannot afford the bandwidth theft.
SolutionsAt one time my webmaster had passwords on his picture files, but that required his visitors to enter a username and password before they could see his galleries. In addition, due to some technical issues, he was unable to protect pictures on the main index or thumbnail pages with that system. He had a lot of bandwidth theft from those areas that he couldn't password protect. He spent allot of time moving files around trying to stay ahead of the bandwidth thieves.
Around the middle of 2006, he discovered a way to use the referring page header information to control access. His server analyzes the referring page field, if the field indicates the page containing the image is located on his site, CowboyFrank.net, or the field data is missing, then the image is sent to the visitor. If the referring page field contains anything else, the image is refused. This puts an additional workload on his server, but has completely eliminated all his bandwidth theft.
If you have a blog on MySpace.com and you try to embed a photo from his server in your "space", or in my case, HorseHints.org, the header lists the referring page as being on "MySpace.com" rather then "CowboyFrank.net", or HorseHints.org, so his server refuses to deliver the image. He has instituted this firewall block on HorseHints.org to circumvent bandwidth theft on my site.
Your problemIf you are unable to see my pictures, your firewall is not just blocking the referring page header field, it is actually replacing it, usually with an advertisement for itself. Sometimes I see a line in my logs such as "field blocked by such-and-such firewall". This doesn't match "HorseHints.org" so is server refuses the request for the image. If your firewall was just blocking the field, leaving it blank, his server would have sent you the image and you wouldn't be reading this.
What can you do?Tell your firewall not to block that portion of the html header, or better yet, get another firewall which isn't trying to promote itself to all the websites you visit. (I might call that reverse popup advertising) The firewall contained in Windows XP SP2 is decent and is part of your operating system. Most of the commercially available firewalls are also good. It is just a few that think they need to stick their name in web server logs which are only seen by an extremely small number of people.
I am told by a visitor that in Zone Alarm the option to show headers is right next to persistent cookies and web bugs.