Re: Proxy Servers (Markus Stumpf)
Date: Thu, 17 Feb 1994 19:45:41 --100
Message-id: <1994Feb17.182421.6427@Informatik.TU-Muenchen.DE>
Precedence: bulk
From: (Markus Stumpf)
To: Multiple recipients of list <>
Subject: Re: Proxy Servers
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Length: 1893

In article <>, (Lou Montulli) writes:
|> Tim I have to disagree.  The code that was in the WWWlibrary 
|> DID NOT send the entire URL unmodified, it sent only the
|> host and path part and it has worked that way for as long
|> as I can remember.

I can remember that the libs used with Mosaic 1.2 and the early 2.0alphas
sent the full URL. I know, 'cause I had to modify the gopher and http
gateways I'd written, after that versions :)

Another proposal :)

|> From: (Kevin Altis)
|> Date: Fri, 11 Feb 94 15:09:43 GMT
|> of the HTTP message is the same. For gopher and ftp, the proxy gateway
|> server will return the data encapsulated as a MIME content type to the
|> client like a normal HTTP message. HTTP MIME content types are returned for
|> all URL requests, regardless of the protocol type of the URL. FTP
|> directories, Gopher directories, etc. are returned as text/html.

I have always wondered, why e.g. gopher gateways should have to
convert the data they gate.
With the new gateway code I hoped we might have an *easy* way to gate
things, simply manage a binary 1:1 connection between client and destination.
But as I understand it this is not the case?
But why should a gateway encode the answer from a gopher server e.g.
wenn a client like Mosaic could do it himself and in a much neater
way with (internal-) icons and so on.

This is what I think we should have:  ;)

WWW_xxx_GATEWAY   send full URL, expect answer in  text/html

WWW_xxx_PROXY     send full URL, expect answer as raw data as from
                  destination server

 Markus Stumpf                        Markus.Stumpf@Informatik.TU-Muenchen.DE