It appears that Abyss does not populate the PATH_INFO server variable the same way that every other server does -- at least not for script-mapped URLs. You should still be able to use URLs that point to foxweb.exe, or use the work-around you discovered.
Sent by Raheel on 05/19/2005 08:49:46 PM:
Oops. I goofed up on one thing. The URL that works is this:
Where index.fwx is a file in 'C:\PROGRAM FILES\FOXWEB\PROGRAMS\' folder and it could be a blank file. It does not matter what is in that file, it will not execute unless you specify: http://localhost/index.fwx /index.fwx.
I think it gets the Abyss Web Server to fire up the FoxWeb and then the next parameters is actually what's executed.
At the risk of confusing someone (even more?), I will add that the URL I gave previously, http://localhost/show_cgi.fwx /show_cgi.fwx will also work if there was a dummy file named show_cgi.fwx in the web server's document root directory.
Sent by Raheel on 05/19/2005 08:36:46 PM:
OK. After hours of messing around with FoxWeb and Abyss Web Server, I finally was able to get them to work together but in a rather unexpected way.
ISAPI Filename Extensions = "dll" [I think this is the default anyway]
Interpreter = "C:\Program Files\FoxWeb\CGI\FoxWeb.exe"
Arguments = <None>
Type = Standard
Use the associated ... = <checked>
Associated Extensions = fwx
Now here is the weird part:
Assuming you are running the whole show on your workstation, typing http://localhost/show_cgi.fwx should logically execute, but instead it gives an error message 'No script was specified in the URL'
It gets weirder:
Try this http://localhost/show_cgi.fwx /show_cgi.fwx
and viola!!! it works
I'm assuming this behavior is not unique to my computer because of all the different configurations I tried. Here are some of the things I tried:
1) Used %1 or even %1 %2 in the arguments field under interpreters
2) Used FoxWeb.dll instead but the result was even worse. With this configuration, I always get an error message "No program root has been configured for domain "" '. Yes that's two quotation marks with nothing in between, indicating an empty string. The error did get logged in FoxWeb control panel and I'm pasting the contents of the 'Memory Variables' tab:
SERVERVARIABLESLEN Local N 51.00 ( 51.00000000) initvars
POSTDATALEN Local N 0.00 ( 0.00000000) initvars
INPUTBUFFER Local C "" initvars
CONTENTTYPE Local L .F. initvars
I Local L .F. initvars
CURLINE Local L .F. initvars
PREVPOS Local L .F. initvars
NEXTPOS Local L .F. initvars
TOTFIELDS Local L .F. initvars
BOUNDARY Local L .F. initvars
UPLOADEDFILENAME Priv C "" initvars
SERVERNAME Local C "" getprogramroot
PROGRAMROOT Local C "" getprogramroot
Obviously the program root is set correctly or I should get the same message using FoxWeb.exe also.
3) Tried arguments with the DLL interpreter also
4) Played around with Scripting Parameters -> Script Paths with no success.
Sent by SinclairZX81 on 01/25/2005 09:33:55 AM:
Has anyone sucessfully configured Abyss Web Server to work with Foxweb? I have already refered to the help documentation about the scripts (CGI) but can't seem to get the foxweb configuration right.
The FoxWeb.exe is loaded in the cgi-bin (scripts) folder of Abyss, and I have loaded the CGI interpreter settings of Abyss as show in the parameters below:
J:\Program Files\Abyss Web Server\cgi-bin\Foxweb.exe
User CGI Environment Variables:
When I try to run a script, for example the sample, http://127.0.0.1/cgi-bin/contact.fwx, the browser returns the message:
HTTP 404 Not Found.
When I attempt to further path out the request using:
I get the foxweb executable to respond, but it answers with the message: Script "CONTACT.FWX" is invalid, or non-existent.
I know it has to be a configuration issue, but am not sure which way to turn, so any help you can give would be appreciated, as I would like to try this fine product. Thanks in advance.