From: SMTP%"VMSGopher-L@trln.lib.unc.edu" 2-DEC-1994 11:28:20.46 To: EVERHART CC: Subj: Re: Can't get server scripts to execute... X-ListName: Gopher for VMS implementation and testing Warnings-To: <> Errors-To: owner-vmsgopher-l@trln.lib.unc.edu Sender: owner-vmsgopher-l@trln.lib.unc.edu Date: Fri, 02 Dec 1994 11:01:50 -0400 (EDT) From: Dave Jones Reply-To: VMSGopher-L@trln.lib.unc.edu Subject: Re: Can't get server scripts to execute... To: VMSGopher-L@trln.lib.unc.edu Message-ID: <01HK5YKNQS9EB3JRJ2@kcgl1.eng.ohio-state.edu> X-VMS-To: IN%"VMSGopher-L@trln.lib.unc.edu" X-VMS-Cc: JONESD MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT From: "Brian R. Kuhn" >>In article , infantino@mary.acornsw.com (Robert Infantino) writes: >> > It appears that my HTTP server isn't making connections via decnet to wwwexec. >> > The following happens: >> >> Here's the HTTP server log for the connect attempt: >> >> TCP-80/1 connect from 140.186.88.9.1039, 2-DEC-1994 08:37:59.10 (20) >> TCP-80/1 http request: 'GET' '/htbin/squashreport', (HTTP/1.0) >> TCP-80/1 request stats: strings=13, bytes=286 >> Rule test failure (protect): '/WWW/HOSTPROT.HTML' vs. '/HTBIN/SQUASHREPORT' >> Rule test failure (protect): '/WWW/USERPROT.HTML' vs. '/HTBIN/SQUASHREPORT' >> Rule test failure (map): '/HELP*' vs. '/HTBIN/SQUASHREPORT' >> Rule test SUCCESS (exec): '/HTBIN/*' vs. '/HTBIN/SQUASHREPORT' >> dnet exec Ident: /HTBIN/SQUASHREPORT*/HTBIN/*www_root:[bin] parse lengths: 19 7, dir: www_root:[bin] >> task specification after default: 'WWW_ROOT:[000000]WWWEXEC.COM' prefix_l=0, bindir: 'www_root:[bin]' >> Testing against 'WWW_ROOT:[000000]WWWEXEC.COM' >> Connect status=324 for task_spec[0] = '$1$FRA100:[WWW.][000000]WWWEXEC.COM' >> TCP-80/1 response stats: hdr = 112, data = 0 bytes >> TCP-80/1 execution completed with status: 1 at 08:38:05.04 >> >> Again, any help is appreciated. >> >> Dick Munroe It looks like you defined a logical name WWWEXEC to point to WWW_ROOT:[000000]WWWEXEC.COM. The server expects a WWWEXEC logical to be an alternate DECnet task specification string (default is 0::"0=WWWEXEC"). If you want WWWEXEC to be someplace other than sys$login for the server account you have to take a round about approach: $ define/sys wwwexec "0::""0=RELOCATED_WWWEXEC""" $ define/sys relocated_wwwexec www_root:[000000]wwwexec >I think we need your rule file. Looks like the problem lies in the MAP, >PASS entries. If you are refering to the funky looking 'dnet exec ident:' line, it is supposed to look like that (matched-path*bindir-path*bindir-directory). ----------------------------------------------------------------------------- David L. Jones | Phone: (614) 292-6929 Ohio State Unviversity | Internet: 2070 Neil Ave. Rm. 122 | jonesd@kcgl1.eng.ohio-state.edu Columbus, OH 43210 | vman+@osu.edu Disclaimer: Dogs can't tell it's not bacon.