Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

We are using WebSense at work, my problem is that they are blocking several sites (ads.google, tweetmeme.com, etc.), that are used in many of the sites I visit, the problem with is that I cant surf a lot of sites anymore, for example trying to go to http://channel9.msdn.com/ it get stuck on loading something from tweetmeme.com (literally waiting hours).

So my question is how can i configure firefox with some kind of timeout so that if the site does not respond in x minutes skip it and try to download the rest of the page. this happens on firefox 3.6.8 and 4 beta 2

Thanks for your time

Juan Zamudio

share|improve this question
    
Will the Websense admin grant access or change settings to allow browsing after the warning is posted? –  Dave M Aug 9 '10 at 20:31
    
What our WebSense does is redirect to an internal page telling you that you are a bad boy, but since most of the sites that I cant surf have this content on an IFrame i don't car about having the content with all that messages also. –  Juan Zamudio Aug 10 '10 at 1:43
add comment

1 Answer

up vote 2 down vote accepted

It sounds like your company's WebSense firewall is pretending to be those sites and accepting connections and requests, but not sending any response back and keeping the connection open. This causes Firefox to just keep waiting forever.

Here are some possible solutions.

  • If you can install Firefox Add-Ons, you might try an add-on that will block the problematic addresses altogether. For example, you can install Adblock Plus and add the following filters

    http://tweetmeme.com/*
    http://*.tweetmeme.com/*

  • If you are on a Windows computer and can download and run executable files, you can try using TCPView to close stalling connections. For example, in the list of connections, you can find the connection from Firefox to tweetmeme.com:http, right-click on it and choose Close Connection. This might be tiresome for regular use, but could be useful if you only need to workaround the stalls occasionally, or to help confirm exactly which sites the firewall is stalling.

(Frustratingly, it looks like Firefox did at one time have a setting to time-out when a server accepted a connection but gave no response -- network.http.request.timeout -- but this functionality was removed.)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.