Hello! Since my upgrade to seamonkey-2 some time ago I noticed that some web pages stopped to load - a blank page was displayed (or old contents remains), the progress indicator is showing that the browser is waiting but nothing happens, there is no network traffic and there are no open network connections. Sometimes the last information on the status bar is something like "waiting for ssl.googlesyndication.com" and similar. Tracking this revealed that because my squid proxy setup blocks some sites like googlesyndication.com, doubleclick.net etc. by acls, when they are accessed by https instead of http, mozilla browsers (tried seamonkey and firefox) got stuck and there is no way loading a (SSL) web page referring to one of the blocked sites. Only removing the block or using another browser (Konqueror and IE work OK) allows to view the page. The problem may be caused by the error message squid sends over the line when a blocked page is requested which probably is not SSL encrypted. So the SSL code gots stuck, it even does not recognize that the TCP connection has been terminated and is waiting forever without a timeout for something. With seamonkey-1 this problem did not show up but latest versions had other encryption issues so I didn't try them lately. It may be a squid bug as well that the error message is encoded wrong but the browser should not get confused. My attempt to generate the bug by trying to load an non-ssl-page over https results in an ssl_error_rx_record_too_long error message so can't provide any other way to trigger the error except to use squid (currently 3.0.19 but this didn't make a difference) with an http_access deny acl to some ssl site. Reproducible: Always
Bug belongs to upstream, file a bug with them and cc mozilla at gentoo.org to the bug report please.
(In reply to comment #1) I have found similar issues there but apparently with no clues on the source. I added my comment to this bug report http://bugzilla.mozilla.org/show_bug.cgi?id=544970 and cc mozilla at gentoo.org.
