Hi, Hector, Have you filed a bug to be specific about which problem you're having? There is a reasonable chance we're working on it, but let's be specific about what the problem is. If you can provide a repro case, that would be great. Also, we're working on some significant changes to the HTTP stack; if you run "chrome.exe --new-http", that will use the new HTTP stack. When you file the bug, please let us know if it is present there too.
Here are the open bugs on digest auth: http://code.google.com/p/chromium/issues/list?can=2&q=digest+auth Thanks, Mike PS - As you know, the tone of your message doesn't help. On Mon, Jan 5, 2009 at 11:53 AM, HLS <sant9...@gmail.com> wrote: > > Excuse me? > > But how long will it take to fix this bug? I just updated my local > copy of chrome and this bug still exist. I hate to sound angry but > this is ridiculous. I can not recommend nor even bother to discuss > Chrome to my customers as an alternative browser as long as it fails > to support the most inherent and most basic fundamental HTTP standard > - BASIC/DIGEST authentication, just like the rest of the majority > browsers do. > > I know Google is trying to push Chrome as the alternative browser, but > lacking proper support for HTTP authentication will continue to dog it > and bad mouth it. So please, its been months since this has been > reported. > > Thanks > > Hector Santos, CTO > http://www.santronics.com > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
