New network code. Google Chrome now has its own implementation of the HTTP network protocol (we were using the WinHTTP library on Windows, but need common code for Mac and Linux). We fixed a few bugs in HTTP authentication and made Google Chrome more compatible with servers that reply with invalid HTTP responses. We need feedback on anything that’s currently broken, particularly with proxy servers, secure (https) sites, and sites that require log in.
WinHTTP was the last item binding Chrome to Windows. With that gone, so go any barriers to Google releasing a version of Chrome for Mac and Linux.2 While a working version of the browser is not yet available for either operating system, it’s only a matter of time now. You can check out the source for the Linux version Google Code
1 From the little that I’ve used Chrome, I’ve found it to be pretty slick but, honestly, I can’t imagine using a browser on a daily basis without Greasemonkey (and the slew of scripts I rely on). So even when Chrome is released for Linux, I’m still going to probably be sticking with Firefox for anything I would consider “work.”