The builds from the trunk, which include this fix, will be coming soon to the dev channel. You can immediately try the latest builds at http://build.chromium.org/buildbot/continuous/LATEST/ although these builds are bleeding edge. Information about joining the dev channel is at http://dev.chromium.org/getting-involved/dev-channel/
Watch for news about the dev and beta channels this week on our official blog at http://blog.chromium.org/ Jon On Mon, Jan 5, 2009 at 1:05 PM, Wan-Teh Chang <[email protected]> wrote: > > On Mon, Jan 5, 2009 at 12:28 PM, Evan Martin <[email protected]> wrote: > > > > It would help if you link to the bug in the bug tracker. > > > > I believe this message is in reference to > > http://code.google.com/p/chromium/issues/detail?id=1629 > > which has been marked fixed. > > This bug has been fixed on the trunk of the Chromium source tree. > But the fix isn't in the latest Google Chrome release yet because > it is based on a branch created in November. We didn't backport > the bug fix to the official branch because it's a big patch so there's > a risk that we may introduce other bugs when we adapt it for the > official branch, which uses a completely different HTTP stack. > > Hopefully the fix will appear in a Dev Channel release as part of > our new HTTP stack very soon. > > Note: the bug is not that Chromium doesn't support HTTP BASIC > and DIGEST authentication. The bug is that Chromium will only > send a HTTP Authorization header after receiving a 401 Authorization > Required response to the first attempt of the request. > > Wan-Teh Chang > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
