W3C home > Mailing lists > Public > www-jigsaw@w3.org > September to October 1999

Re: Jigsaw proxy - using protocol...

From: Yves Lafon <ylafon@w3.org>
Date: Mon, 6 Sep 1999 15:17:56 +0200 (MET DST)
To: Semuel Vomberg <semuel@vipe.technion.ac.il>
cc: www-jigsaw@w3.org
Message-ID: <Pine.GSO.4.10.9909061516220.9047-100000@tarantula.inria.fr>
On Mon, 6 Sep 1999, Semuel Vomberg wrote:

> On Thu, 2 Sep 1999, Yves Lafon wrote:
> 
> > > > The Jigsaw client will try (if possible) to use HTTP/1.1 connections, as
> > > > this protocol is far better as HTTP/1.0 regarding cache semantics.
> > > > So if a client is sending an HTTP/1.0 request to a Jigsaw proxy, the
> > > > request issued by the proxy will be HTTP/1.1
> > > 
> > > but if we look at HttpBasicServer class, at doRequest function, we'll find
> > > the line "switch (getRequestMode(request))" and from this I got my
> > > conclution. am I wrong ?
> > 
> > Well, the manager can perform HTTP/1.1 and HTTP/1.0 requests, the
> > ProxyFrame is responsible for the creation of that request, based on the
> > incoming request.
> > see org.w3c.jigsaw.proxy/ForwardFrame, the method is :
> > protected org.w3c.www.protocol.http.Request dupRequest(Request request) 
> > And the request that will be sent is...
> > 	req = manager.createRequest();
> > which is by default an HTTP/1.1 request.
> 
> hmm. so why that switch (at HttpBasicServer), if the server will use
> HTTP/1.1 anyway ?

The server yes, but the Client stack may be reused in other application,
and you can then specify the HTTP level you want. Also, depending on the
remote server's reply, Jigsaw's client stack will adapt itself to the
protocol level of the remote server, this is particulary useful when a PUT
or a POST has to be performed (handling of 100-Continue and others).
Regards,

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Monday, 6 September 1999 09:18:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:33 GMT