From: SourceForge.net <no...@so...> - 2007-08-18 13:55:46
|
Feature Requests item #1776724, was opened at 2007-08-18 05:27 Message generated for change (Comment added) made by fabiankeil You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=361118&aid=1776724&group_id=11118 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Fabian Keil (fabiankeil) Summary: HTML error messages should only be sent with HTML files Initial Comment: When a file's transfer (from the server to Privoxy) is interrupted*, I think HTML error messages ("503, This is Privoxy ...") should only be sent (to the browser) if the file being transferred is a HTML file. I am asking for this change, because of the following: 1. If the file is not a HTML file, the error messages won't be displayed anyway (if you send the error messages after, say, a partially-transfered JPEG file, they will be interpreted by the browser as part of the partially-transferred image and won't be displayed as HTML). 2. Mozilla Firefox 1.5 (and probably some other browsers as well), when encounters an interrupted file transfer, when the transfer is retried (e.g., when Go button is clicked again), will try to resume the transfer from the point the transfer was interrupted (if you send the error messages after, say, a partially-transfered JPEG file, they will be interpreted by the browser as part of the partially-transfered file, corrupting the file). *) "Interrupted file transfers" are unsuccessful file transfers where there are already part of the file (this includes the file's HTTP headers) being sent to the browser. ---------------------------------------------------------------------- >Comment By: Fabian Keil (fabiankeil) Date: 2007-08-18 13:55 Message: Logged In: YES user_id=875547 Originator: NO If an ongoing file transfer is interrupted Privoxy isn't supposed to send any error message. Please show us an excerpt of Privoxy's log file that shows how Privoxy is sending it's own error message after already delivering parts of the original content (or just explain how to reproduce it). This would be a bug, no matter whether or not the original content was an image or not. If you can't do that, this request will be closed as invalid. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=361118&aid=1776724&group_id=11118 |