Re: libwww, a different approach
Tim Bunce (Tim.Bunce@ig.co.uk)
Thu, 16 Mar 1995 13:09:25 +0000
In article <9503151754.AA15493@getafix> you write:
>In <199503151544.JAA12696@gate.ti.com>
>On Wed, 15 Mar 1995 15:39:55 +0000
>Martijn Koster <m.koster@nexor.co.uk> writes:
>> > What my scheme allows is
>> >
>> > ftp_proxy=ftp://ftp.proxy
>> > telnet_proxy=telnet://telnet.proxy
>> >
>> > IE not all proxies have to be proxied to http
>> > This is required for people like me who sit behind firewalls and to
>> > telnet out I have to do a proxy telnet to a get machine.
>>
>> Can you give an example of what happens when you telnet through
>> your library?
>
>The library calls a callback routine with either 4 or 8 arguments
>
> URL host/port/login/passwd
> PROXY host/port/login/passwd
>
>all the proxy could be undf if not being proxied.
>
>The proxy I need to use for telnet
>
>telnet_proxy=telnet://gate.ti.com
>
>The callback which I use invokes a xterm echos some info then telnets to gate
>
>the info echo'd is enough to ask the user to login to thier proxy account
>and it also echos the host/port/login/passwd for the remote site
>
>Here is the code
>
>sub do_telnet {
> my $host = shift;
> my $port = shift;
> my $user = shift;
> my $pass = shift;
>
> my $phost = shift;
> my $pport = shift;
> my $puser = shift;
> my $ppass = shift;
>
Hopefully we'll end up with these being passed as two url objects.
I hope to produce a summary message in the next couple of hours
that may take us a step forward.
Graham, could you send me your current code? I'd like to take a look
and I can put it on an ftp site for you.
>Regards,
>Graham.
>
Regards,
Tim.