W3C home > Mailing lists > Public > www-jigsaw@w3.org > July to August 1997

Re: List of jigsaw proxy problems - bug fix ?

From: Yael Stav <stav@radview.com>
Date: Thu, 07 Aug 1997 17:59:13 +0300
Message-ID: <33E9E2C1.4725A2A4@radview.com>
To: jigsaw mailing list <www-jigsaw@w3.org>
CC: Anselm.Baird_Smith@sophia.inria.fr
To all jigsaw fans,

In a previous message I sent to the mailing list, I mentioned a problem
in using jigsaw as a proxy (client side):
Requesting specific URL's results in a "Document contains no data" from
the browser.

I think we eventually figured out what the problem was:
When the HTTP response is HTTP/1.1 and has no Content-Length Jigsaw is
supposed to wait for the server (who owns that resource) to close the
connection.
The problem is that Jigsaw closes the connection by itself instead.
Notice that w3c.www.protocol.http.Reply calls in that case (no
content-length, no
"chunked" input stream but still HTTP/1.1) the notifyFailure() method.
of  HttpBasicConnection.java:

public synchronized void notifyFailure(InputStream in) {

   markIdle(true);
}

The call to markIdle(true) will close the socket, free all data
structures of the connection,
and delete the connection from the server. I think it should ONLY delete
it from the
server (for it cannot be reused).
Hence:

    public synchronized void notifyFailure(InputStream in) {

        ((HttpBasicServer) server).deleteConnection(this);
    }

This code change does fixes the problem, still I'd like to have some
confirmation about it, since I would not like to damage anything else.

Any comments will be appreciated.
Thanx.
--
Yael Stav
RadView Software Ltd.      email : stav@radview.com
Tel-Aviv, ISRAEL         voice:   +972-3-6459013
http://www.radview.com     fax:     +972-3-6471406
Received on Thursday, 7 August 1997 10:59:57 GMT

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