www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wojciech Szenajch <...@csbi.waw.pl>
Subject mod_proxy/747: Incomplete files cuted by broken transmission are proxy-cached.
Date Wed, 18 Jun 1997 13:40:01 GMT

>Number:         747
>Category:       mod_proxy
>Synopsis:       Incomplete files cuted by broken transmission are proxy-cached.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Jun 18 06:40:01 1997
>Originator:     wsz@csbi.waw.pl
>Release:        1.2
Solaris 2.4: SunOS ns 5.4 Generic_101945-43 sun4m sparc
gcc version
The problem was experienced also in Apache 1.2b8, 1.2.b10. I have not tested
other versions.
Problem is mabye similar to 314, but files are not to short, but incomplete.
The file may have even several hundreds of kilobytes.

When transmission breaks during loading a file, file stays cuted on local harddisk
(using Netscape 3.0) and in Apache cache. Pressing "Reload" or trying iniciate
transfer from another machine ends with receiving uncomplete file from Apache 
proxy cache. There is no way of deleting such file from WWW browser. The only
solution for user is to disable cache in browser and reload file again. This
cleans browser, but not Apache proxy.

It happened to ftp like file transfers but also to gif being part of html page.
I have 1Mb/s link and this problem is not easy to reproduce. It happens once
for few days on slow connections to other sites. But not always.

Mabye check the status of incompete files in proxy cache and what happens when
the transfer is stopped by network (not by user). Is the status changed in this
situation? Is there any difference in status of complete nad uncomplete file%3

View raw message