InformAction Forums

I started getting 'Connection Interrupted' in firefox once i updated to 1.9.3.3. For example, go to slashdot.org then try and click on the discussion link and that error pops up. I disabled noscript, restart firefox and the error goes away.

also this is on windows xp with firefox 3.0.10. Tested on two seperate XP loads. I havent tested on the redhat ws 5 load yet to see if it is happening there as well

I have been getting this too but ONLY when I have a heavy bandwidth load up until recently (running torrent or something) otherwise very sparse. Giorgio, it might be worth looking into, its becoming chronic. Profile/Environment combination tested/affected:

Fx 3.0.10/WinXP Sp3
Fx 3.5 pre/WinXP Sp3
Fx 3.0.10/Ubuntu
Fx 3.0.10/Win 7 RC
Fx 3.0.10/Vista x86 Sp2

I cannot reproduce at all.
Maybe an extension conflict?
Could you try Standard Diagnostic keeping NoScript enabled all the time?

(Error loading websites)

I have been getting this too

Too? Too in general, or too specifically at http://www.slashdot.org/?
And too with 1.9.3.3 or with earlier versions too?

Too in general. It happens more on https sites and no, I am not enforcing anything.

I'm getting this too, using firefox 3.0.10, on ubuntu linux 8.10, using noscript 1.9.2.8.

by this, i mean on slashdot, when trying to click a link to the discussion, I get a "page load error, connection interrupted"

I suspect though, that it is not having to do with noscript itself, but rather with having javascript disabled. The reason is that trying to use "wget" to get the target discussion pages, or lynx, or really any other way that doesn't have javascript, fails just as well.

maybe this bug should be filed with slashdot?

i don't think it is related to a connection speed issue. My wifes XP system and mine both had this issue and we ran a 25 man WoW Ulduar raid with no lag for 3 hours with 23 others. Our kids were browsing around the internet via our squid proxy/iptables firewall and they were not complaining either about the connection.

Anyhow I just tested it on a VMware instance running CentOS 5.3 final running Firefox 3.0.10-1.el5. I upgraded the NoScript plugin and the slashdot forums broke again (now on a different network, different OS etc). No other plugins are installed. I disable NoScript via the Add-ons menu item and I can browse the discussion forums again.

The common issue with all the systems is that they were all running the latest Mozilla plugin version of NoScript but when I read the release notes on needing to upgrade to the latest version from noscript.net, I went ahead and upgraded the machine at that point (instead of using the Mozilla addon page).

Quick update: enabling javascript for slashdot.org doesn't fix it, but enabling javascript for fsdn.com fixes the "page load error" problem on slashdot.

Looks like Slashdot broke something against Flash-blockers in general, see this Mozillazine thread.
Not NoScript-specific, definitely.

Finally someone elucidated what needed to be done to see the error.

Allright I broke out the wireshark and discovered the problem with slashdot.

It is stupid cookies support. If you disable/disallow cookies (and I have slashdot on deny all cookies) the "Read More" link does not work. The server actually sends a tcp ACK for the initial browser HTTP GET, but then also immediately sends a tcp RESET packet.

I disabled/disallowed cookies in firefox and, yep, the "Read More" link fails here too.

slashdot <--------- FAIL

http://forums.mozillazine.org/viewtopic ... 5#p6584135

URL: http://slashdot.org/
Article: News: Wikipedia Bans Church of Scientology

NoScript. slashdot.org NOT Allowed.
Slashdot cookies cleared.

Click that article.
Page opens as expected.

Back-arrow to http://slashdot.org/.

Article: News: Wikipedia Bans Church of Scientology
Now click the Read More... "button" at the bottom of the blurb for that article.

This URL trys to load, http://news.slashdot.org/story/09/05/29/0114236/Wikipedia-Bans-Church-of-Scientology.

Instead you get:
(Connection Interrupted The document contains no data. The network link was interrupted while negotiating a connection. Please try again.)


Allow slashdot.org.
Now click the Read More... "button" at the bottom of the blurb for that article.

Same result.

Forbid slashdot.org.
Allow fsdn.com.
Now click the Read More... "button" at the bottom of the blurb for that article.

Same result.

Allow both slashdot.org & fsdn.com.
Now click the Read More... "button" at the bottom of the blurb for that article.

Now the page opens properly from the Read More... link.

Back-arrow to http://slashdot.org/.
Revoke Temporary Permissions (so that neither slashdot.org nor fsdn.com are allowed).

At that point all the Read More... links still continue to work.

Now clear your slashdot.org cookies.

Things break again.

Just a spam magnet now. Locking.