NOTE: FoxWeb version: 4.6.3
- Same result running VFP9.EXE or VP9 runtime
- Same result IIS6 or IIS7.5
- Same result Windows7 Professional (localhost)
PROBLEM MIGHT BE RELATED TO SCRIPT-MAPPING
- I can duplicate the problem by unchecking: [ ] Use Web server's directory mapping in FoxWeb Control Center or by checking the box and deleting my Fw_start solution that checks for a valid URL.
Sent by FoxWebUser1998 on 08/23/2016 08:05:37 AM:
I agree. I expected to see FoxWeb's own error-handler.
In my scenario, my browser shows "Waiting for localhost". FoxWeb produces no initial, error message, and the channel times-out with the FoxWeb message: "FoxWeb Message The FoxWeb service has returned the following message:
Foxweb Timed Out--"
FW_start LOG EXCERPT:
08/23/2016 08:51:45 Restarting Channel 2
08/23/2016 08:54:17 Killed Channel 2: /firstname.lastname@example.org [ALTERED SCRIPT -- I ADDED "aaaa" in URL bar]
08/23/2016 08:54:24 Restarting Channel 2
I've worked-around using FW_start, but because there are no errors, there is no ther information I can provide.
The problem is the same on "Localhost" development and on Windows Server 8 R2, but had same experience on Windows Server 2003.
Sent by FoxWebsupport on 08/23/2016 01:40:20 AM:
Channels should not be hanging when a non-existent script is requested in the URL. What exactly are you experiencing?
FoxWeb Support Team
Sent by FoxWebUser1998 on 08/22/2016 12:32:23 PM:
What is the easiest way to prevent FoxWeb from hanging a channel while trying to run a non-existent script if someone alters the url string? For example, if the URL "...Finduser.fwx" was changed to "...Findme.fwx" where "...Findme.fwx" does not exist? I created a file-list that is searched by Fw_enter, but is there something easier than listing 100-plus possibilities?