Clayton, Aparajita, et. al., Thanks for the suggestions. I checked it out and found that this web site came up on A4D 4.5+. There was no upgrade. I compared the A4D 4.0 OWC method and was not certain how to retrograde.
I did take the suggestions of two others on the 4D Tech NUG. One of them seems to have done something positive toward alleviating the graphic loading problem. If it did, the problem came from a MS service pack to WS 2003 OS. My web page request was being interpreted by the OS as a denial of service attack. This makes sense because the failing graphic load request did not reach 4D Server. I adjusted the registries following: http://kb.4d.com/search/assetid=76127 I tried but could not get the OS to work correctly (serve all graphics) unless I complete disabled the denial-of-service feature of the OS. Another developer suggested that I copy all my images and js files to the static web folder, maintaining the directory structure, and allow 4D to serve them directly. He solved this same problem that appeared only with SSL. I tried his solution and it did not seem to make any difference for my graphic loading failure. I tested both SSL and non-SSL. They both failed similarly for me. As of my last test (feels like egg shells) all my graphics are loading, after disabling the denial-of-service feature of the WS 2003 SE SP1&2. I posted this message for others who may need it. Thanks!! David Ringsmuth -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Donahue, Clayton L. Sent: Wednesday, November 17, 2010 2:13 PM To: [email protected] Subject: Re: [Active4d-dev] graphic loading failing > A4D 4.5+ Hi David, This may or may not be a red herring, but I'll throw it out there. We had a similar issue when first upgrading to 4.5, from 4.0. We were running 4D 2004.X (can't remember exactly). It had similar symptoms: intermittently, some images requests would seem to fail, especially if there were lots of small images on the page. We tracked it back (in our case) to "On Web Connection". A4D 4.5 was doing something different, where it was trying to avoid copying the response blob (note #926 in the 4.5 release notes). When we restored this section to the way it worked in A4D 4.0 (actually copying the blob), our issues went away. The section of code in 4.5 looks like this: [code] TEXT TO BLOB("\r\n";$headerBlob;Text without length ;*) SEND HTTP RAW DATA($headerBlob;*) SEND HTTP RAW DATA(A4D_Response) [/code] Maybe take a look at "On Web Connection" in 4.0 or 5.0? Also, perhaps check your keep-alive settings? Good luck! - Clayton _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/ _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
