cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9538] - CachingOutputStream doesn't handle severed connections
Date Thu, 06 Jun 2002 11:36:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9538>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9538

CachingOutputStream doesn't handle severed connections





------- Additional Comments From stuart.roebuck@adolos.co.uk  2002-06-06 11:36 -------
I've now pinpointed why we were hitting against this problem so much, and it
may be of interest to others.

If you are serving an audio file using Cocoon to a Windows machine with
Windows Media Player set up to play audio files, then Internet Explorer asks
for the file and starts downloading it, and (presumably noticing that it is
an audio file) it terminates the download and passes on the job to Windows
Media Player which then re-requests the file.

Prior to the bug fix for this issue, this pretty much guaranteed that the end
user would receive a truncated audio file (because the terminated transfer
resulted in a truncated file being cached and then returned).  With the bug
fix it means a lot of stack dumps in the error log.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message