LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CGI's are not processing LabVIEW InternetToolkit 8.2.1

You may also want to make sure that you are accessing your webpages under the G Web Server with a URL like:

http://localhost:81/examples/accpanel.htm

The ":81" is necessary in order to tell your web browser that it should use port 81 rather than the default port 80. I hope this helps!

Regards,

Casey Weltzin
Applications Engineer
National Instruments

 

0 Kudos
Message 11 of 14
(1,145 Views)
Phil,
 
I am a long time user of the internet toolkit as well. Currently I am stuck with the same problem as you are, having to share a port 80 between a web panel application and the g-web server (for user/pswd authentification). If the built in web server could handle cgi calls we would not be stuck having to do this at all.
 
What I have come up with is this : sharing port 80 works fine in LV7.1, it does not work in 8.2.1, acording to NI it works again in 8.5. When port 80 is enabled both as the G-web server and as the built in web server, the CGI's are not executed as cgi's, but rather treated as static files, the G web server therefore makes your browser download the CGI instead of executing it. Running the system on two ports is of course easy and works, but is a firewall nightmare that will never work in any free country 😉
 
Let me know if you find any solution, I think I am returning to LV 7.1.
 
søren h jensen
 
p.s. I am running a carpool database programmed in LabVIEW on the site www.pendler.dk. Originally programmed in PERL in 1996 its been operating in LabVIEW the last 7 years. I have very few crashes and the G webserver is completely imune towards any kind of remote attack. The cgi extention ".vi" is not that common 🙂
0 Kudos
Message 12 of 14
(1,135 Views)
søren,
 
Since I do not at the moment really need to do any input processing in the CGI I was using and found a workaround for my needs, I have not looked closely at the HttpServer.vi. I did take a short look and it seems that it may be possible trace through HTTPServer and figure out where the problem is I'd start with isCGI and HTTP CGI Run Q Handler. It is possible a local variable is no longer being set or a default has changed.
 
BTW: I have installed the 6.0f2 ITK patch, the change may have been introduced then since I did not have this problem in LV 8.2.
 
Phil Bailey
0 Kudos
Message 13 of 14
(1,132 Views)

Hi Phil,

With the option Share LabVIEW Web Server Port turned on (using port 81), I am able to access my CGI VIs without problems (both the G Web Server and the LabVIEW Web Server are enabled). I am using LabVIEW 8.2.1 as well, so I think that we may have slightly different settings from each other.

Are you accessing your CGI VIs using <hostname>:81 format? What happens if you try to share port 80 and then access your CGI VIs from the server machine? I am sure that we can work together to determine what is happening here.

Regards,

Casey Weltzin
Applications Engineer
National Instruments

0 Kudos
Message 14 of 14
(1,126 Views)