>I would like to create a Metacard stack to log into a web server, and
>post data to a particular URL.  This stack must be able to
>authenticate with the server.
>
>Could someone who has experience in this area post a simple example
>script that  illustrates the following:
>
>1) Connecting to an http web server from Metacard
>2) log into server by correctly formatting and delivering a supplied
>username and password to the server (ie authenticate to the web
>server).
>4) download some HTML and display it in a card
>3) POST some data  from MC to web server. This posting could include
>uploading a file on the disk (eg a zip archive, word document,
>whatever) to the server.
>
>What I want to do is replace a web form (which includes a file upload
>option for graphics and documents) with a Metacard stack, in order to
>automate and simply some processes.
>
>I imagine this has been covered before, but I wasn't able to find an
>answer on a quick trawl through the MC list archives.  Anyway, any
>help would be gratefully appreciated.
>
>I am imagining that the above might be achieved by doing the following:
>
>1) open socket to server  http:<my server>/
>2) read data from socket, detect authentication challenge (?), write
>appropriate authentication data to socket (?)
>3) open new socket to server http:<my server>/<path to...>.cgi
>4)POST data to CGI  by writing same to new socket
>- Confirm receipt of data
>5) close all sockets
>
>If someone is prepared to post some practical information on how to
>go about doing the above, I will format it into a nice example stack
>with links to all the relevant documentation, and make it available
>to anyone who is interested.

The most efficient way to go about this in my opinion is to use the mchttpd
stack as guide for how things can work, do the research on the appropriate
protocol and  start working on it. From your description above I gather you
have a pretty good understanding of how to approach it.
I suggest using an address of type
"http://www.user:[EMAIL PROTECTED]/dir/script.cgi" for authentication. The
cgi checks the user/password and reads from socket the file to be uploaded.
If authentication fail the cgi returns an error.

>
>Rodney
>--
>
>************************************************************
>Rodney Tamblyn
>HEDC, 33 Union Street, University of Otago, P.O. Box 56, Dunedin, New Zealand
>email     [EMAIL PROTECTED]
>Phone   64 3 479 7580   Fax  479 5194  ICQ  4145098  PGP available
>************************************************************
>
>This is the MetaCard mailing list.
>Archives: http://www.mail-archive.com/metacard%40lists.best.com/
>Info: http://www.xworlds.com/metacard/mailinglist.htm


Regards, Andu



This is the MetaCard mailing list.
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm

Reply via email to