SOLUTION: As it turns out, the problem was caused by the fact that the Sun Web Server version 7 does not like relative Location HTTP headers. If a Location header does not start with "http://", or "https://" the server immediately returns a 408 HTTP status to the browser.

FoxWeb Support Teamsupport@foxweb.com email

Sent by David Hempy on 10/01/2008 08:56:12 PM:

I have been running FoxWeb as an application (that is, with the channel windows visible) throughout my testing. As I said in my first post, the very first line of fw_enter.prg is a print statement, and that statement is not appearing in the channel windows. Also, the title of the channel windows never changes to reflect a busy status.

I agree with you about the timeout value (I've left it at 15 seconds),
but that's not the issue...the error is returned to the browser
instantly.

This exact code runs just fine on the old hardware...I've done byte-wise compares between the .prg and .fxp files between the two with no discrepancies. I'm quite certain that my code never gets executed when the Broker
gets in this state. There are no dialog boxes, illegal commands, or user
inputs.

Do you have any other suggestions of things I can check for or known issues? I've been actively developing this site in FoxWeb for over a decade, but I've plumb run out of ideas on this problem.