www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Kraemer <Martin.Krae...@Mch.SNI.De>
Subject mod_proxy/314: Truncated (short/invalid) files are proxy-cached. Ought to be invalidated.
Date Fri, 04 Apr 1997 15:10:01 GMT

>Number:         314
>Category:       mod_proxy
>Synopsis:       Truncated (short/invalid) files are proxy-cached. Ought to be invalidated.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Apr  4 07:10:01 1997
>Originator:     Martin.Kraemer@Mch.SNI.De
>Organization:
apache
>Release:        1.2b8-dev
>Environment:
SVR4 on MIPS and intel
>Description:
When a transmission via an intranet apache proxy (which forwards via 
ProxyRemote * http://firewall) receives a "short" file
(i.e., transmission stops before Content-Length bytes have arrived),
the short file is put into the cache nonetheless.

IMHO, this is the easiest situation to decide that the file should be invalidated (removed),
instead of happily re-serving the truncated file on a reload (if the reload
sends no no-cache header, as Mosaic does by default).
>How-To-Repeat:
Hmmm... can you force a truncated transmission? Should be possible via a
nph-Script with a Content-Length that is too big.
>Fix:
Remove temp file instead of putting it in cache hierarchy if it is too short
>Audit-Trail:
>Unformatted:



Mime
View raw message