Re: CGI/1.0 status

• Mail folder: WWW Talk Oct 93-present
• Next message: Ari Luotonen: "Re: CGI/1.0 status"
• Previous message: Dave_Raggett: "X Mosaic, FTP and PASV"
• In-reply-to: Ari Luotonen: "Re: CGI/1.0 status"
• Reply: Ari Luotonen: "Re: CGI/1.0 status"

Date:  2 Dec 93 10:31 -0800
From: George Phillips <phillips@cs.ubc.ca>
To: <luotonen@ptsun00.cern.ch>
Cc: <robm@ncsa.uiuc.edu>, <www-talk@nxoc01.cern.ch>
In-reply-to: <9312020956.AA11673@ptsun03.cern.ch>
Message-id: <6981*phillips@cs.ubc.ca>
Subject: Re: CGI/1.0 status

Ari:
>Why does nph: (or now nph-) have to be present in the URL at all? -- It's
>information controlling the server.  I would prefer it being in the
>script filename suffix, automatically added by the server when searching
>for executable.  If you want to change a previously normal script to
>an nph- script you would have to modify all the docs containing URLs
>to that script.  If .nph is added by server no docs need to be changed.

Ah, yes, I knew there was some other reason why "nph-" in the URL
can cause you trouble.  However, I believe this is not a problem
under NCSA HTTPD because you can use ScriptAlias to hide the
script name (right?).  Even without the "nph" problem I'd use
scriptalias anyways -- no need to hard-code script names into the
URL.

I'll assume plexus is only one line of perl code away from a
similar mechanism, but maybe the CERN server can't do ScriptAlias
as easily.  Certainly I'd go along with Ari's suggestion, but
it may be a little painful for DOS, NT, OS/2 users -- they may
depend on .exe suffixes to execute things, I think.

			-- George