Author | Topic: Development path problem | |
---|---|---|
Bruce Anderson | Development path problem on Thu, 17 Feb 2005 07:52:28 -0600 I want to look at a web I am creating while it is on my "development" server, SERVER-4, using IE on either that server or from a workstation on the LAN. SERVER-4 is running IIS ver.6.0. Assuming, for simplicity: Registered domain name is "abc123.com" In IIS, under "Properties" for the site: The Description of the website is "abc123" IP address 192.168.1.4 TCP port 80 The host header values in IIS: www.abc123.com, 192.168.1.4 and abc123.com, 192.168.1.4 The home directory: "c:\inetpub\wwwroot\abc123" This site has a virtual directory: "cgi-bin", local path "c:\inetpub\wwwroot\cgi-bin" Here is my problem. When I enter http://localhost/abc123 (or http://server-4/abc123 from my workstation ) I do get back my index.htm page which contains a form and has these code lines below: <FORM name="Login" onsubmit="return Validator(this);" ACTION="/cgi-bin/waa1gate.isa" METHOD=POST> <input type=hidden name="WAA_PACKAGE" value="MY_ABC123"> <input type=hidden name="WAA_FORM" value="CHECKLOGIN"> When I submit the form, it fails with an "incorrect address page can't be displayed error HTTP 405". I think this means that the form submittal is not going where I want it to go, i.e., it does not have a correct path to waa1gate.isa. Of course, this all works perfectly fine in the internet real world. My heartache is in my development side. I assume it has to do with the ACTION parameter. What would I make it read so that the code will work locally and over the internet, and can it be done without having a separate version for each kind of access? I appreciate your time and wisdom. Bruce Anderson | |
Vladimir Iahnenco | Re: Development path problem on Thu, 17 Feb 2005 09:23:17 -0500 Hi Bruce, I see you managed to make IIS6 working Try your code without "onsubmit" macro. You also may try to remove METHOD="POST", from my best knowkedge waa1gate accepts only GET requests. -- Regards, Vladimir "Bruce Anderson" <banderson@graphical-db.com> wrote in message news:3YevegPFFHA.6160@S15147418... > I want to look at a web I am creating while it is on my "development" > server, SERVER-4, using IE on either that server or from a workstation on > the LAN. SERVER-4 is running IIS ver.6.0. > > Assuming, for simplicity: > Registered domain name is "abc123.com" > In IIS, under "Properties" for the site: > The Description of the website is "abc123" > IP address 192.168.1.4 > TCP port 80 > The host header values in IIS: > www.abc123.com, 192.168.1.4 and abc123.com, 192.168.1.4 > The home directory: "c:\inetpub\wwwroot\abc123" > This site has a virtual directory: "cgi-bin", local path > "c:\inetpub\wwwroot\cgi-bin" > > Here is my problem. When I enter http://localhost/abc123 (or > http://server-4/abc123 from my workstation ) I do get back my index.htm page > which contains a form and has these code lines below: > <FORM name="Login" > onsubmit="return Validator(this);" > ACTION="/cgi-bin/waa1gate.isa" > METHOD=POST> > <input type=hidden name="WAA_PACKAGE" value="MY_ABC123"> > <input type=hidden name="WAA_FORM" value="CHECKLOGIN"> > > When I submit the form, it fails with an "incorrect address page can't > be displayed error HTTP 405". I think this means that the form submittal is > not going where I want it to go, i.e., it does not have a correct path to > waa1gate.isa. Of course, this all works perfectly fine in the internet real > world. My heartache is in my development side. I assume it has to do with > the ACTION parameter. What would I make it read so that the code will work > locally and over the internet, and can it be done without having a separate > version for each kind of access? > > I appreciate your time and wisdom. > Bruce Anderson > > | |
Phil Ide | Re: Development path problem on Thu, 17 Feb 2005 14:49:21 +0000 Bruce, > Try your code without "onsubmit" macro. Yes, keep things simple until you have them working. If a simple form can work, but adding the validator causes it to fail, the problem is in your validator... > You also may try to remove METHOD="POST", from my best knowkedge waa1gate > accepts only GET requests. No, waa1gate accepts POST and GET equally well. GET is only suitable for small amounts of data. When a message is sent via GET, the web-server creates a shell into which it launches the cgi program (waa1gate.exe). Within the shell, the webserver creates an environment variable to contain the GET data. Many operating systems have a limit on the size of an environment variable (and some have limits on the size of the environment!), so data that is too large can get truncated. This is where POST comes in, and it was created to alleviate this problem. The webserver pushes the data (your form variables) into the STDIN for the cgi shell, and waa1gate.exe then reads STDIN (i.e. the keyboard buffer) to retrieve them. If there is insufficient space in the keyboard buffer for all the data, the webserver will wait until the keyboard has been read before pushing in more - until the complete data has been sent to the cgi application. Regards, Phil Ide *************************************** * Xbase++ FAQ, Libraries and Sources: * * goto: http://www.idep.org.uk/xbase * *************************************** I did NOT escape....they gave me a day pass. | |
Vladimir Iahnenco | Re: Development path problem on Thu, 17 Feb 2005 10:20:57 -0500 Hi guys, Phil you are right, I mixed that up with winhttp requests to wa1gate. Alternatively it is possible to test this issue from the IE address bar http://localhost/cgi-bin/wwa1get.isa?WAA_FORM=xxxx&WAA_PACKAGE=xxxx&MyVar=xx xx -- Regards, Vladimir "Phil Ide" <phil@idep.org.uk> wrote in message news:1q2d0jabcel6r$.dlg@idep.org.uk... > Bruce, > > > Try your code without "onsubmit" macro. > > Yes, keep things simple until you have them working. If a simple form can > work, but adding the validator causes it to fail, the problem is in your > validator... > > > You also may try to remove METHOD="POST", from my best knowkedge waa1gate > > accepts only GET requests. > > No, waa1gate accepts POST and GET equally well. GET is only suitable for > small amounts of data. > > When a message is sent via GET, the web-server creates a shell into which > it launches the cgi program (waa1gate.exe). Within the shell, the > webserver creates an environment variable to contain the GET data. Many > operating systems have a limit on the size of an environment variable (and > some have limits on the size of the environment!), so data that is too > large can get truncated. > > This is where POST comes in, and it was created to alleviate this problem. > The webserver pushes the data (your form variables) into the STDIN for the > cgi shell, and waa1gate.exe then reads STDIN (i.e. the keyboard buffer) to > retrieve them. If there is insufficient space in the keyboard buffer for > all the data, the webserver will wait until the keyboard has been read > before pushing in more - until the complete data has been sent to the cgi > application. > > Regards, > -- > Phil Ide > > *************************************** > * Xbase++ FAQ, Libraries and Sources: * > * goto: http://www.idep.org.uk/xbase * > *************************************** > > I did NOT escape....they gave me a day pass. | |
Bruce Anderson | Re: Development path problem on Thu, 17 Feb 2005 08:57:50 -0600 Trust me, fellows, the onsubmit javascript is not the problem. This site has been running fine with this script for a year+ and the script returns an "alert" with the problem description which would tell me it has failed. Ditto for POST versus GET issue; it works. I am guessing the failure has to do with my workstation (or my development server) not knowing where "/cgi-bin/waa1gate.isa" is supposed to be, a DNS kind of problem, maybe. | |
Phil Ide | Re: Development path problem on Thu, 17 Feb 2005 17:57:10 +0000 Bruce, > Trust me, fellows, the onsubmit javascript is not the problem. This > site has been running fine with this script for a year+ and the script > returns an "alert" with the problem description which would tell me it has > failed. Ditto for POST versus GET issue; it works. > > I am guessing the failure has to do with my workstation (or my > development server) not knowing where "/cgi-bin/waa1gate.isa" is supposed to > be, a DNS kind of problem, maybe. Go to http://www.fiddler.com and install fiddler. Launch Internet Explorer and click on the fiddler icon in the toolbar and tell it to begin capture. In IE, browse to the failing URL then switch back to fiddler and for each entry in the left hand pane, examine the HTTP headers (both sent and recieved) in the right hand pane. You may find the answer is there... Regards, Phil Ide *************************************** * Xbase++ FAQ, Libraries and Sources: * * goto: http://www.idep.org.uk/xbase * *************************************** I'll never forget the....uhh...the...never mind! | |
Bruce Anderson | Re: Development path problem on Thu, 17 Feb 2005 12:16:20 -0600 This will be a hoot! Perfect, but I think my fix is to make a DNS entry that is authoritative over the domain and make a www "A" record to point to my development server. And then access it in the regular way of http://www.abc123.com eschewing the "localhost" rigamarole. Muy grande brain fade moment on my part. BTW, www.fiddlertool.com "Phil Ide" <phil@idep.org.uk> wrote in message news:v9ovayu6kzj6.dlg@idep.org.uk... > Bruce, > >> Trust me, fellows, the onsubmit javascript is not the problem. This >> site has been running fine with this script for a year+ and the script >> returns an "alert" with the problem description which would tell me it >> has >> failed. Ditto for POST versus GET issue; it works. >> >> I am guessing the failure has to do with my workstation (or my >> development server) not knowing where "/cgi-bin/waa1gate.isa" is supposed >> to >> be, a DNS kind of problem, maybe. > > Go to http://www.fiddler.com and install fiddler. Launch Internet > Explorer > and click on the fiddler icon in the toolbar and tell it to begin capture. > > In IE, browse to the failing URL then switch back to fiddler and for each > entry in the left hand pane, examine the HTTP headers (both sent and > recieved) in the right hand pane. You may find the answer is there... > > Regards, > -- > Phil Ide > > *************************************** > * Xbase++ FAQ, Libraries and Sources: * > * goto: http://www.idep.org.uk/xbase * > *************************************** > > I'll never forget the....uhh...the...never mind! |