Quote:>Oh, your program runs on the web server, it's not a web client. So it
>can't access any web server, only the one it's installed on.
Yes that is correct. It is what I emant all the way through but my
descriptive powers are flawed:)
Quote:>Many ISP's will not allow CGI use on shared web servers, only on web
>servers dedicated to a single client.
So an ISP such as demon.co.uk who do not allow cgi with their standard
accounts would place a cgi account, if they did such an account, on a
different drive or run a web server on a totally seperate box? So they
would have something like this:-
===========================
Standard web accounts, with no cgi usage written by the client=
1 Web Server, serving webpages/users:-
http://www.foobar1.deamon.co.uk
http://www.goobar1.deamon.co.uk
http://www.hoobar1.deamon.co.uk
http://www.ioobar1.deamon.co.uk
Pages physically stored maybe (not important to this thread)
/usr/www/f/a/ etc etc etc
/usr/www/f/o/o/foobar1
etc etc etc
/usr/www/i/a/ etc etc etc
/usr/www/i/o/o/ioobar1
===========================
Where as various accounts with cgi usage written by the client=
seperate Web Servers, serving each accounts webpages:-
http://www.foobar1.deamon.co.uk
Pages physically stored maybe (not important to this thread) on box
number 1 which is running a web server. Path could be:-
/usr/www
etc etc etc
http://www.ioobar1.deamon.co.uk
Pages physically stored maybe (not important to this thread) on box
number 4 which is running a web server. Path could be:-
/usr/www
===========================
I think NOT, as I can hardly see an ISP have a seperate box per cgi
account unless they have a seperate drive or box per cgi account, with
all accounts seerved from one server wheich has access to each seperate
drive or box containing each cgi account.
If however the cgi account holder called hoobar1 has his webpages on the
same drive as the other account holders:-
http://www.foobar1.deamon.co.uk (standard, no cgi)
/usr/www/f/a/
/usr/www/f/o/o/foobar1
/usr/www/f/o/o/foobar1/index.html
/usr/www/f/o/o/foobar1/non-linked_file
/usr/logs/f/o/o/foobar1/access_log
/usr/ftp/f/o/o/foobar1/
http://www.goobar1.deamon.co.uk (standard, no cgi)
/usr/www/i/a/
/usr/www/i/o/o/ioobar1
http://www.hoobar1.deamon.co.uk (full cgi)
/usr/www/i/a/
/usr/www/i/o/o/ioobar1
/usr/www/i/o/o/ioobar1/index.html
/usr/www/i/o/o/ioobar1/cgi-bin (containing my prorgams)
http://www.ioobar1.deamon.co.uk (standard, no cgi)
/usr/www/i/a/ etc etc etc
/usr/www/i/o/o/ioobar1
In this case my 2 programs work as I suggest! I have an initial html
page that uses GET to pass the requested stuff:-
http://www.hoobar1.co.uk/cgi-bin/cgiwrap/hoobar1/program?up=treepath
&treepath=%2F&files=on&recurse=off
?up=treepath
&treepath=%2Fusr (/usr)
&files=on (Display files=on)
&recurse=on (Recurse directorys=on)
So the program extracts from the GET method the path requested and
options. It then does a read dir and displays what it reads back to the
browser. Then you can click on the directory or file, if on a directory
the same program is ran again if a file is clicked on, another program
is called which either displays the file or downloads it.
Quote:>And some web servers can be
>configured to change to a different userid depending on the virtual host
>that was accessed; customers can protect their files by making them
>readable only by their userid -- your CGI will only be able to read
>world-readable files. Some web servers can even use chroot() to restrict
>the parts of the filesystem that the server can access.
Not too sure about what you mean here. How do I test my legitamisy
without causing problems, i.e. I had best not give the 2 programs over
publically?
Mark.
--
Mark Worsdall (Webmaster) - WEB site:- http://www.shadow.org.uk
Shadow:- webmasterATshadow.org.uk
Home :- shadowwebATworsdall.demon.co.uk
Any opinion given is my own personal belief...