Tuesday, June 14, 2005

Controversy Over ‘Phoenix UFO Video’ Continues to Heat-Up!

UFO Phoenix 2005-2 Resampled Sharpened BDR

By Frank Warren

     In response to Santiago Garza’s contentions  that the images Brian Bessent  (www.ufotheatre.com) has maintained to have  taken on “June 5th,” were in fact “published earlier,” Bessent writes:

     A person named santiago Yturria GARCIA [sic] (pictured at left)is spreading false rumors around the internet about the 6-5-05 ufo sighting to attempt to discredit the ufo footage because its too real and he can't accept the reality of it so he spreads a lie saying that the search engine GOOGLE had somehow cached images from the sighting before it was online.

     This lie is absurd and its a flat out lie. google did not cache ANY ufotheatre.com picture and the .HTM file that he claims is proof of it was nothing more than the fact that the old .html file has references to the new files that were updated on our ufotheatre.com web site AFTER the google page was cached.

     There is absolutely NO PROOF on earth that google ever cached anything accept an old htm file. because the images on that supposed cached page can be changed anytime we update OUR site with NEW IMAGES... Making old google htm files useless for anything other than starting up cheese easily disproved LIES!

     More . . .

     Yesterday Garza responded, "I received this information from Google regarding their cache. Please read it carefully."

     "Google automatically takes a 'snapshot' of each page it crawls and archives it. This 'cached' version allows a webpage to be retrieved for your end users if the original page is ever unavailable (due to temporary failure of the page's web server).

     The cached page appears to users exactly as it looked when Google last crawled it, and we display a message at the top of the page to indicate that it's a cached version. Users can access the cached version by choosing the "Cached" link on the search results page.

     It's clear the webpage with the UFO images was retrieved on May 28, 2005. Brian knows it and we all know by now."



  1. Brian is correct. Google only caches the HTML code of the page but it does not cache the images.

    The cache will show new images if the file names in the cache are the same as the new images.

    I received an email from Santiago about his message from google and I replied that I can prove that what google told him is not exactly true.

    I'm not trying to prove or disprove the validity of the AZ footage but I can prove that Santiago's argument that those images were on the ufotheatre.com site on May 28 is not valid.

  2. Terry Writes:

    You can prove that Google only caches the html by looking at the source of the cahed page. The BASE href="your server" element is added. The html code for an image stays the same as it was in the original copy of the page as found on the site. But just adding that BASE tag insures that the image is referenced from whatever server you put in the attribute: in this case, Google has defined it as


    Even if you don't look at the source code, you can verify the truth of the matter if you use Firefox. Right-click and choose view image, and look in the address bar. Alternatively, you can look at the properties for images too (in IE as well) and it will tell you at what location the image is at.




Dear Contributor,

Your comments are greatly appreciated, and coveted; however, blatant mis-use of this site's bandwidth will not be tolerated (e.g., SPAM etc).

Additionally, healthy debate is invited; however, ad hominem and or vitriolic attacks will not be published, nor will "anonymous" criticisms. Please keep your arguments "to the issues" and present them with civility and proper decorum. -FW