I am the network administrator for an Australian K-12 school. We are cross platform, and support both Mac & Windows environments, based of an Active Direct… (funda kabanzi)
I am the network administrator for an Australian K-12 school. We are cross platform, and support both Mac & Windows environments, based of an Active Directory Infrastructure.
We have local proxy server based on ISA 2006, using McAfee SmartFilter as the local filtering solution.
The issue I am having has been occuring since Firefox 12 was released. A number of websites retrieved through firefox started using the HTTPS connection by default, for example google.com, youtube.com, twitter.com, or carrying out a search using the search bar.
For example - If i search cat in the search bar, Firefox will automatically refer the search through this url - https://www.google.com.au/search?q=cat&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-GB:official&client=firefox-a&channel=fflb.
With the majority of our Mac computers running Firefox 14 or later, this search is hampered and returns the message Proxy is refusing connection. To overcome this, I have trained staff and students to remove the 's' from http:// and to reattempt the connection. If it isn't a blocked term, ie porn, the proxy will ask for login details, and connect through.
In the case of a blocked website, such as YouTube, the same fix is applied to bring up the block page, which can allow the override. Further more, once the filtering is turn off. The issue doesn't rear again, until the filter cuts back in.
This also occurs, but less often with our Windows based computers running Firefox, as they support NTLM authentication straight through.
What makes it most curious, is that Safari versions 5 & 6, the current and many releases of Google Chrome, and Internet Explorer 7, 8 & 9 work flawlessly.
I'm looking for an option or a fix that will allow us to set a preference the HTTP over HTTPS for these website so that Firefox can at least work straight out, prior to the release of this feature, or adjust so that if the connection is refused/unable to connect by the proxy at, it will try by HTTP before failing to connect.
If there is anything else I can try, please let me know.