> -----Original Message-----
> From: Andu [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 23, 1999 12:07 PM
> To: [EMAIL PROTECTED]
> Subject: RE: More questions about mchttpd server
>
>
> >I think I must be doing something fundamentally wrong here.
>
> You are indeed: echo.mt only works on UNIX type OSes.
> As I said before the ability of the server to process plain
> MC scripts is
> in the works.
Oops. I misread Scott's message to say it worked on NT. Apparently I just
skipped over the part that said "can easily be extended to..."
At any rate, since I love to torture myself, I decided to move everything
over to UNIX and try again there. I followed all of the same steps outlined
below, except the UNIX machine where I copied stuff is called "miami" and my
personal directory on miami is "mcentor".
Using the file selector, mchttpd came up with "/u/mcentor/cgi-bin" as my
root, but the correct path to display the text of echo.mt from my HTML file
was "//miami/mcentor/cgi-bin/echo.mt", so I also tried
"//miami/mcentor/cgi-bin" as the root, and I also tried deleting the
"/cgi-bin" from both those paths, since I'm still not clear on whether the
root is supposed to be the folder housing mchttpd or the folder housing the
cgi-bin folder that houses mchttpd. In any case, none of these permutations
worked, including trying both 1080 and 8080 as the port. In all cases, IE
tells me "The page cannot be displayed" and the title bar says "Cannot find
server." Oh, and I checked the permissions on all my files:
read/write/execute for me, read/execute for all others.
I'm obviously missing something, but I have no idea what. I've got this
great MetaTalk parsing routine that will do all kinds of magical things to
the data from my HTML forms, if I could only reach the server. I feel like
the answer is just out of reach...
If anyone's got any idea what else I should try, please let me know. Thanks
for all your patience & help so far.
Marni
>
> > Perhaps if I
> >describe exactly what I've done, someone could point out my
> error(s) or
> >omission(s). I'm working on NT.
> >
> >1. On a network drive known as "winntdoc" and mapped to my
> machine as "N:",
> >I created a directory called "Marni" and within that I created a
> >subdirectory called "cgi-bin".
> >
> >2. I copied the following files to this directory: mc.exe, mchome.mc,
> >mctools.mc, mchttpd_0.1b.mc, echo.mt, survey.mt,
> MChttpd.log, MChttpd.conf,
> >and the .gif files that came with the mchttpd download.
> >
> >3. I opened MetaCard and then opened mchttpd_0.1b.mc.
> >
> >4. I changed the settings in mchttpd to Port=1080 and
> Root=N:/Marni/cgi-bin,
> >and clicked SET to save the settings.
> >
> >5. I clicked the START SERVER button.
> >
> >6. I created a simple web page containing a form with one
> field and a submit
> >button. The HTML for the form is:
> ><FORM ACTION="http://winntdoc/Data Drive/Marni/cgi-bin/echo.mt"
> >METHOD="POST" ENCTYPE="application/x-www-form-urlencoded">
> ><INPUT TYPE="Text" NAME="Marni"><INPUT TYPE="Submit" NAME="Submit"
> >VALUE="Submit">
> ></FORM>
> >
> >When I open the web page and enter text in the field and
> then click Submit,
> >IE tells me "The page cannot be displayed" and the IE title
> bar says "HTTP
> >501 Not Implemented."
> >
> >I also tried setting the root to N:/Marni, //winntdoc/Data
> Drive/Marni and
> >//winntdoc/Data Drive/Marni/cgi-bin (without changing the
> HTML code at all),
> >but got the same result with each of these.
> >
> >If I change the HTML code to say "file:" instead of "http:",
> the text of
> >echo.mt displays in the browser, so I know I've got the
> right path set in
> >the HTML code. I figure I must be doing something wrong
> with the server
> >setup, because my HTML page echoes properly to
> >http://www.metacard.com/cgi-bin/echo.mt. Any ideas?
> >
> >I'd really appreciate any help that anyone can provide.
> >
> >Thanks,
> >Marni
>
> Regards, Andu
>
>
----------------------------------------------------------------------------
--------------------
The views and opinions expressed in this email message are the sender's
own, and do not necessarily represent the views and opinions of Summit
Systems Inc.
