We switched between the protocols by enabling and disabling the following entries in Firefox’s about:config page:Įach test was performed in a fresh instance of Firefox with an empty browser cache. The performance test used HttpWatch with Firefox to run a series of simple page load tests against the Google UK home page using the three protocols: It has new columns to display information about the protocols being used by each request: We also updated HttpWatch this week so that it supports HTTP/2 within Firefox. Google is now supporting HTTP/2 draft 14 on its web servers alongside the SPDY protocol giving us a chance to compare the performance of raw HTTPS, SPDY and HTTP/2 on the same web page. The HTTP/2 specification has not been finalised so Firefox actually enabled the Draft 14 version of HTTP/2 but little is expected to change in the final draft. Januin Firefox, HTTP/2, HTTPS, HttpWatch, SPDY, SSLįirefox 35 was released this week and became the first browser to enable support for the HTTP/2 protocol by default. UPDATE: You can still Firefox 40 to test HTTP/2 with HttpWatch by downloading it from Ī Simple Performance Comparison of HTTPS, SPDY and HTTP/2 UPDATE: Mozilla is also deprecating the XPCOM and XUL technologies that have been the foundation of the Firefox extension system. It will work with HttpWatch version 10 and receive security fixes until approximately March 2016. If you want to carry on using HttpWatch, for as long as possible, the best option is to use Firefox ESR version 38. We have come to the conclusion our development time would be better spent adding more features to HttpWatch on Internet Explorer and adding new ways to sniff HTTP traffic from other browsers. The rapid 6 week release cycle has made it increasingly difficult for developers and Firefox users to keep their extensions working with each new release. It’s not just the dropping of binary extension support that has forced this decision. Unfortunately, porting the HttpWatch extension to JS/XUL or using JS c-types is not feasible due to the large development effort required, the inability to maintain a low performance overhead and the limited interfaces available to the underlying Firefox web and network components. The main reason is that Firefox 41 will drop support for native extensions like HttpWatch: Sadly, the last Firefox version HttpWatch will support is 40 (the one released this week, August 11, 2015). HttpWatch added support for Firefox 2 & 3 back in 2008 and we’ve updated it to support the 39 major versions released since then.
0 kommentar(er)
