on 5/18/06 6:20 PM, Aparajita Fishman at [EMAIL PROTECTED] wrote: > You are getting 200 back from Active4D, but that doesn't mean the > file was not found, it could mean that Active4D has returned its > error message successfully. > > That isn't the problem, it's normal behavior. Browsers ask for > favicon.ico on every request if they don't have one for the current > domain. If it isn't there it is ignored, it doesn't affect the rest > of the site.
Aparajita: We just followed Brad's suggestion and dropped a favicon.ico file into the web folder. While it didn't solve the problem, we are looking at another source. In trying to trace through the OWC after the trace, we had problems with the debugger window being partially off-screen. We have resized it and saved it, but it doesn't seem to "take," as it returns to it's over-large size with each call to A4D. FWIW, it now seems to return the 200, but then we no longer see the request for the icon file. FWIW, the first parameter on the 200 shows (I think) that the original file requested was "default.a4p" and not the 404 file you provided (which IS the one being displayed). At the moment, we're suspecting some file corruption may be causing all of these problems. The debugger window resizing problem seems to indicate this, and it may well be the cause of the other problems as well. We'll investigate this and report back -- probably sometime tomorrow. Meanwhile, thank you all for responding as quickly as you did. We had spent a couple of days on this already and were becoming mighty frustrated. Now at least it seems like we're on the road to solving the problem (we hope). Thanks again . . . Tom Lundeen TLC - Tom Lundeen Consulting Prairie Solutions, Inc. _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
