NTLMv1 auth has been disabled, NTLM support on non-Windows platforms is now deprecated
The support for the NT LAN Manager version 1 (NTLMv1) network authentication has been disabled because it’s known as insecure. Companies and organizations still deploying the older protocol should upgrade to NTLMv2. See Honza Bambas’ blog post and Jason Duell’s post to the dev-planning list for details.
This is affecting SharePoint-based or IIS-backed intranet applications. If you encounter any problems on Firefox 30 or later, you can manually enable NTLMv1 using a preference. Note that NTLMv2 is not supported on non-Windows platforms, so OS X and Linux users have to toggle the preference to continue using NTLMv1 as below, though the NTLM auth support on non-Windows platforms is considered deprecated.
How to enable NTLMv1: type
about:config in the location bar, click the “I’ll be careful” button, find
network.negotiate-auth.allow-insecure-ntlm-v1, double-click on it to change the value to
Another workaroud here is using Firefox 24 ESR that still enables the NTLMv1 auth.
For developers and consumers alike, successful W3C and Ecma International web standards are important for making the web better. A comprehensive test suite is an important part of a healthy standard, along with a clear specification and great implementations of the standard. Without thorough tests that assess the normative statements in a specification, a proposed standard is just a document on a website.
Any browser can claim to support some or all of a specification. The test results from a comprehensive test suite are the best way to determine which browsers will render the same markup consistently. Web developers have told us that seeing the test results, chapter-by-chapter, spec-by-spec, enables them to spend their valuable time building rich, interoperable web experiences for their customers.
We developed 75 new test cases and updated 168 test cases in conjunction with development of Internet Explorer 10 Release Preview. The IE Testing Center now offers a total of 7573 test cases. We continue to work closely with these two web standards organizations by submitting these test cases officially within each working group’s official process.
We welcome your continued feedback on the test cases using the appropriate W3C mailing list for each working group. For ES5 test cases please open bugs in the test262 bug database.
The first table below summarizes the test results by specification with Internet Explorer 10 Release Preview along with each of the major shipping browsers running on the Windows Release Preview. The second table at the bottom of this page provides links to each of the test cases we submitted to each appropriate working group to help the web become more interoperable.
Cross-browser Test Results Summary:
||Number of Submitted Tests
||Internet Explorer 10 Release Preview
||Mozilla Firefox 12
||Apple Safari 5.1.7
||Google Chrome 19.0.1084.46
||Internet Explorer 9
|SVG 1.1 2nd edition
Great news, the greatest little open source web debugger, Fiddler, has now been aquired by the great vendor of .NET controls, Telerik. Expect some nice upgrades to Fiddler soon, and yes, it will remain free.
“We have some very exciting news to share with the Telerik community. Telerik has just acquired Fiddler! Even more exciting is that Fiddler’s brilliant creator Eric Lawrence will come over from Microsoft to join the team fulltime. For those of you who don’t know, Fiddler is a web debugging proxy which logs all HTTP(S) traffic between your computer or device and the Internet. In other words, it is an essential tool for any web, desktop or mobile developer. The popularity and sophistication of Fiddler is hugely impressive considering this has been Eric’s informal side project for more than 8 years. With Eric joining the team he will be able to deliver on his vision for Fiddler with the full financial and resource backing of Telerik.
It might be apparent why Eric would jump at an opportunity to turn his side passion project into a full time position, but what might not be readily obvious is why Telerik would need a product like Fiddler in our portfolio.
Our strategy has always been to acquire when it makes sense and to use the new technology to improve our core products for the benefit of our customers. In the case of Fiddler, this was a natural extension because Fiddler is already in use as the core technology behind Test Studio’s load and performance features. Additionally, we gain a formidable competitive edge over other tools as both Eric and Fiddler join the Test Studio product family. The collaboration for enhancing Fiddler is already underway as well as discussions to further expand our portfolio and extend support for our customers.
The Fiddler community is very important to us. We have learned from the mistakes of others who have acquired free tools only to turn the tables on the community and monetize them at a later date. We admire what Fiddler has delivered to the community and want to expand that value by investing in things like expanded platform support, user interface improvements and a first class website with extensive community and support features.
That is why, as part of our commitment to keeping Fiddler free and making further investments into the tool, we have launched a poll on the Fiddler website asking the community to vote on the first improvements we will target. Whether you are an avid or occasional Fiddler user we would love to get your opinions on what you would like to see happen first.
To give you some insight into how popular Fiddler really is here are some stats, year to date. On average Fiddler receives over 9,000 installations EVERY DAY, and when I say average that is including weekends. That number jumps to over 10,000 for weekdays. The website has received more than 5 million unique visitors this year alone with over 80% of them being first time visits. Needless to say that the Fiddler community is not just big, it’s HUGE.
So please help me in welcoming Eric and the Fiddler community into the Telerik family. Great things are ahead for Fiddler as we continue to invest in and build an even better tool and community. To see how Fiddler is already powering Test Studio’s load and performance features download a trial today.”
As SharePoint developers we are bound to IE but often fallback to other browsers for various reasons such as performance, HTML standards compliance, or in my case with Firefox – the plugins available. The official Technet on what is and is not supported on various browsers (Chrome is notably not even in there): http://technet.microsoft.com/en-us/library/cc263526.aspx. I will follow up this post with a list of what specifically will not work with SharePoint when using Firefox (so you can’t say I didn’t warn you!)
While Google Chrome is definitely a solid choice, if you are using Firefox the following plugins will help you out:
Various network tweaks that deliver a zippy experience. This will also speed up your SharePoint user experience greatly too.
- Prefetch Links
Dynamic speed increases can be obtained with Fasterfox’s unique
prefetching mechanism, which recycles idle bandwidth by silently
loading and caching all of the links on the page you are browsing.
- Tweak Network
Fasterfox allows you to tweak many network and rendering
settings such as simultaneous connections, pipelining, cache,
DNS cache, and initial paint delay.
- Page Load Timer
A millisecond accurate page load timer tests the effectiveness
of your settings.
- Block Popups
A popup blocker for popups initiated by Flash plug-ins is also
1. Remember, just because you’ve got a turbocharged browser doesn’t mean your colleagues or clients do. This plugin is a double-edged sword because you can get lazy or indifferent about performance problems on web applications. If you are developing, testing, or QA’ing systems you should either use a different browser (COUGH IETester COUGH) or temporarily disable Fasterfox.
2. The out of the box setting in the Firefox > Add-Ons > FasterFox > Options menu is “Optimized“. Set that bad boy to “Turbo Charged” and to hell with playing nice with server resources – our time is worth more!
Windows Media Player Plugin for Firefox
Description: Lets you run Windows Media content in Firefox. In particular you will be able to stream WMV videos such as the ones we have in the newly minted it groove SharePoint center directly in your browser window.
Web Developer Toolbar
Description: Adds a toolbar with a slew of options essential for anything webby. CSS, Forms, Images, Cookies, Viewing Source – instantly get Xray vision into any web page.
iMacros for Firefox
Description: Automate Firefox. Record and replay repetitious work. If you love the
Firefox web browser, but are tired of repetitive tasks like visiting the
same sites every days, filling out forms, and remembering passwords,
then iMacros for Firefox is the solution you’ve been dreaming of!
***Whatever you do with Firefox, iMacros can automate it.***
Description: With ColorZilla you can get a color reading from any point in your
browser, quickly adjust this color and paste it into another program.
You can Zoom the page you are viewing and measure distances between any
two points on the page. The built-in palette browser allows choosing
colors from pre-defined color sets and saving the most used colors in
Basic end-user usage could be grabbing the color code for the blue from a clients logo and matching it up to another design element.
Description: Firebug integrates with Firefox to put a wealth of web development tools
at your fingertips while you browse. You can edit, debug, and monitor
Firebug also is required for Yahoo YSlow and the Google Pagespeed Firefox Plugins