ack sent.
Forwarded message:
> From tahmed@on.bell.ca Tue Oct 17 09:08:36 1995
> Date: Tue, 17 Oct 1995 12:08:03 -0400 (EDT)
> From: tahmed <tahmed@on.bell.ca>
> X-Sender: tahmed@tasha.development.bcsc.bell.ca
> To: apache-bugs@mail.apache.org
> Subject: hey
> Message-Id: <Pine.HPP.3.91.951017115842.1788A-100000@tasha.development.bcsc.bell.ca>
> Mime-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hey guys. There doesn't seem to be a general email address,
> so I just thought I'd write to this. Not really a bug, but a suggestion.
> I wouldn't stay strict to the setup structure of NCSA, be
> your own server! You should look at the CERN server and see what it has
> to offer, and incorporate it's good features as well.
> One feature that's missing from NCSA/Apache is the amount of
> control over the ScriptAlias directive. If you look at CERN it has
> a similar thing called Exec, but it can use wild cards.
> With the NCSA if i want a cgi to be run when someone goes to
> /specialdir then you go ScriptAlias /specialdir /usr/local/specialcgi
> But any url with the specialdir string in it, will still get redirected
> to specialcgi.
> With CERN I can tell it /specialdir/* so that it runs everything
> that comes after that string. Or I can go /specialdir/ /specialcgi and
> only when a person goes /specialdir it will run that specialcgi. But
> will return regular html files with anything appended onto
> /specialdir like /specialdir/whatsnew.html. Where as the NCSA/Apache server
> will end up running specialcgi if I go /specialdir/whatsnew.html.
> An example in practice is http://www.spyder.org/BOP/, it has
> a ScriptAlias to run a cgi that generates a different homepage everytime
> you access it. But all the associated files and directories are inside
> the /BOP structure. So if you access them as /BOP/whatever.foo it still
> runs that cgi. Not good. So what I do to get around this is make a
> symbolic link from BOP to bop. And it just references everything in the
> lower case bop directory, even though the directories are the same. Quite
> the workaround.
>
> ----===<<* BELL SYGMA TELECOM SOLUTIONS *>>===--- /
> 160 Elgin St. Tel: 613-781-9820 //HP Workstation:
> Room 250 Fax: 613-567-2482 /// $4000 Monitor
> Ottawa, Ontario Internet: tahmed@on.bell.ca \\ /// $20000 Computer
> K2P 2C4 IIS: TAHMED \\// $3 Mouse
> http://www.spyder.org/ratt/ \/
>
>
Forwarded message:
> From tahmed@on.bell.ca Tue Oct 17 09:08:36 1995
> Date: Tue, 17 Oct 1995 12:08:03 -0400 (EDT)
> From: tahmed <tahmed@on.bell.ca>
> X-Sender: tahmed@tasha.development.bcsc.bell.ca
> To: apache-bugs@mail.apache.org
> Subject: hey
> Message-Id: <Pine.HPP.3.91.951017115842.1788A-100000@tasha.development.bcsc.bell.ca>
> Mime-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> Hey guys. There doesn't seem to be a general email address,
> so I just thought I'd write to this. Not really a bug, but a suggestion.
> I wouldn't stay strict to the setup structure of NCSA, be
> your own server! You should look at the CERN server and see what it has
> to offer, and incorporate it's good features as well.
> One feature that's missing from NCSA/Apache is the amount of
> control over the ScriptAlias directive. If you look at CERN it has
> a similar thing called Exec, but it can use wild cards.
> With the NCSA if i want a cgi to be run when someone goes to
> /specialdir then you go ScriptAlias /specialdir /usr/local/specialcgi
> But any url with the specialdir string in it, will still get redirected
> to specialcgi.
> With CERN I can tell it /specialdir/* so that it runs everything
> that comes after that string. Or I can go /specialdir/ /specialcgi and
> only when a person goes /specialdir it will run that specialcgi. But
> will return regular html files with anything appended onto
> /specialdir like /specialdir/whatsnew.html. Where as the NCSA/Apache server
> will end up running specialcgi if I go /specialdir/whatsnew.html.
> An example in practice is http://www.spyder.org/BOP/, it has
> a ScriptAlias to run a cgi that generates a different homepage everytime
> you access it. But all the associated files and directories are inside
> the /BOP structure. So if you access them as /BOP/whatever.foo it still
> runs that cgi. Not good. So what I do to get around this is make a
> symbolic link from BOP to bop. And it just references everything in the
> lower case bop directory, even though the directories are the same. Quite
> the workaround.
>
> ----===<<* BELL SYGMA TELECOM SOLUTIONS *>>===--- /
> 160 Elgin St. Tel: 613-781-9820 //HP Workstation:
> Room 250 Fax: 613-567-2482 /// $4000 Monitor
> Ottawa, Ontario Internet: tahmed@on.bell.ca \\ /// $20000 Computer
> K2P 2C4 IIS: TAHMED \\// $3 Mouse
> http://www.spyder.org/ratt/ \/
>
>