Proxy bug?

["Philip A. Prindeville" <ph...@enteka.com>]

Has anyone else noticed that when you use the FTP proxy in Apache
with Netscape, when you "Save to..." a file, the size of the
file (and estimated time remaining) is always "unknown".  Why is
this?  I haven't looked at traces with tcpdump, but does the proxy
not pass back the size of the file to the browser?

-Philip

Re: Proxy bug?

[Marc Slemko <ma...@worldgate.com>]

Apache doesn't take the reported size of the file and translate it into a
Content-Length.  It could.  It already does a SIZE on the file, but you
would have to change it to do something other than throw away the size
returned (it only looks at the status code) and then use it later.

Grr.  

The proxy sends:

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Date: Tue, 30 Sep 1997 01:18:54 GMT

as a response to a ftp proxy request.  This means it is sending an
unchunked response without Content-Length or Connection: close.

That whole section is an ugly hack.  Perhaps the best thing is to just
replace SERVER_PROTOCOL with either a PROXY_SERVER_PROTOCOL or an explicit
HTTP/1.0.  It is easy enough to add a Connection: close, but I wonder if
it is worthwhile or if there may be other 1.1 problems.  The proxy is in
never-never land there...

On Mon, 29 Sep 1997, Philip A. Prindeville wrote:

> Has anyone else noticed that when you use the FTP proxy in Apache
> with Netscape, when you "Save to..." a file, the size of the
> file (and estimated time remaining) is always "unknown".  Why is
> this?  I haven't looked at traces with tcpdump, but does the proxy
> not pass back the size of the file to the browser?
> 
> -Philip
>