Issue 297: Can't login to WRT54G management I/F http://code.google.com/p/chromium/issues/detail?id=297
Comment #8 by [EMAIL PROTECTED]: OK, this is another WinHTTP limitation. If the pwszUserName argument to WinHttpSetCredentials is an empty string (L""), WinHttpSetCredentials fails with the ERROR_INVALID_PARAMETER error (87). Another WinHTTP user reported the same bug at the bottom of the WinHttpSetCredentials MSDN page (look for "Community Content"): http://msdn.microsoft.com/en-us/library/aa384112(VS.85).aspx So switching to our new HTTP stack is the only way to fix this bug. I tried username="" and password="foobar" in the new HTTP stack, and I found that we called Base64Encode with input ":foobar", which is correct. (The output is "OmZvb2Jhcg==".) I will add a unit test for an empty username and close this bug. Issue attribute updates: Owner: [EMAIL PROTECTED] Labels: -OS-All -Area-Compat OS-Windows Area-BrowserBackend NewHTTP -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
