W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 1997

Proxying PUTs

From: Anselm Baird_Smith <abaird@www43.inria.fr>
Date: Thu, 23 Jan 1997 19:07:04 +0100 (MET)
Message-Id: <199701231807.TAA21564@www43.inria.fr>
To: Gordon Dakin <gad@hunchuen.crystaliz.com>
Cc: www-jigsaw@www10.w3.org
Gordon Dakin writes:
 > 
 > 
 > Awhile back, I nearly succeeded in making proxied PUTs work.
 > To do so, I borrowed a few methods from ForwardDirectory,
 > including w3c.www.protocol.http.Request dupRequest(Request request).
 > In that method, I set output stream from a local file:
 > 
 >     if (mth.equals("PUT"))
 >     {
 >         try
 >         {
 >             FileInputStream iStream = new FileInputStream(mypath);
 >             req.setOutputStream(iStream);
 >         }
 >         catch (java.io.FileNotFoundException x)
 >         {
 >             System.out.println("File not found");
 >         }
 >     }

I am not sure I remember the problem, Jigsaw proxy does (by default)
proxy put request properly (at least that's what the code is intended
for).

 > The only glitch is, the content length of the remote Jigsaw's
 > FileResource is always wrong (around 100) when reaches the remote host,
 > so FileResource.newContent() hangs (in the in.read loop) or only gets
 > part of the file.
 > 
 > Do you know what I can set locally to ensure that the remote Jigsaw's
 > FileResource will have the correct content length?

I am lacking some context, could you provide more infos ?

Thanks,
Anselm.
Received on Thursday, 23 January 1997 13:07:22 GMT

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