Re: URL's (was Re: Perl 5 LWP Design)
Martijn Koster (m.koster@nexor.co.uk)
Thu, 09 Mar 1995 08:23:04 +0000
> > If you were to keep the proxy info separate, the request() method
> > should be passed a "this should be proxied to such-and-such" argument
> > (probably the URL of the proxy). The HTTP implementation should then
> > use $url->str() or $url->path() in the HTTP request depending on
> > wether it's a proxy or a normal request. The implementations of all
> > other protocols should then complain if they are asked to proxy,
> > because they can't.
>
> Why ("other protocols should then complain")? Is this in the specification?
> Even if it is, I don't see why WE should have other protocols complaining.
>
> They should also respond to proxy handling appropriately. Even assuming
> a proxy server can only handle http proxy requests (is this the case -
> I haven't checked out proxy servers?), you may still have the situation
> where clients behind a firewall may have proxy ftp, gopher, ... servers.
I'm talking about the protocol implementation. If someone wants
"http://whatever" via proxy "gopher://somewhere", and the gopher
protocol doesn't support proxy'ing, then it should complain.
> I think its not too much trouble to let the libwww be a bit intelligent.
> Perl5 libwww should be designed well enough that it should be relatively
> easy to subclass the base classes to create a client which used a mail
> server proxy to get all types of non-interactive URLs (i.e. not telnet).
Of course.
-- Martijn
__________
Internet: m.koster@nexor.co.uk
X-400: C=GB; A= ; P=Nexor; O=Nexor; S=koster; I=M
X-500: c=GB@o=NEXOR Ltd@cn=Martijn Koster
WWW: http://web.nexor.co.uk/mak/mak.html