Issue 1629: HTTP BASIC and DIGEST Authentication not passed once login  
takes place
http://code.google.com/p/chromium/issues/detail?id=1629

Comment #4 by sant9442:
I had problem downloading the source code, but I pulled what I needed from  
SVN
webviewer.  According to the source net\base\auth_cache_unittest.cc, it has  
a test
for various urls and the expected authenticated translation:


TEST(AuthCacheTest, HttpKey) {
   scoped_refptr<net::AuthChallengeInfo> auth_info = new  
net::AuthChallengeInfo;
   auth_info->is_proxy = false;  // server auth
   // auth_info->host is intentionally left empty.
   auth_info->scheme = L"Basic";
   auth_info->realm = L"WallyWorld";

   std::string url[] = {
     "https://www.nowhere.org/dir/index.html";,
     "https://www.nowhere.org:443/dir/index.html";,  // default port
     "https://www.nowhere.org:8443/dir/index.html";,  // non-default port
     "https://www.nowhere.org";,  // no trailing slash
     "https://foo:[EMAIL PROTECTED]/dir/index.html",  // username:password
     "https://www.nowhere.org/dir/index.html?id=965362";,  // query
     "https://www.nowhere.org/dir/index.html#toc";,  // reference
   };

   std::string expected[] = {
     "https://www.nowhere.org/WallyWorld";,
     "https://www.nowhere.org/WallyWorld";,
     "https://www.nowhere.org:8443/WallyWorld";,
     "https://www.nowhere.org/WallyWorld";,
     "https://www.nowhere.org/WallyWorld";,
     "https://www.nowhere.org/WallyWorld";,
     "https://www.nowhere.org/WallyWorld";
   };

   for (size_t i = 0; i < arraysize(url); i++) {
     std::string key = net::AuthCache::HttpKey(GURL(url[i]), *auth_info);
     EXPECT_EQ(expected[i], key);
   }
}

Based on this expected design criteria shown about, the operational  
behavior would be
incorrect.  For example, for all the variant urls including sub-folders  
etc, the same
key is expected:

     "https://www.nowhere.org/WallyWorld";,

Now I have been trying to trace this down to where the actual  
authentication is being
down (BASIC or DIGEST calculation) and its not straight forward where in  
the code
this is code.

But I am hoping that someone more familiar with the code can use this clue  
to begin
fixing the behavior.    The unit test indicated what is expected for the
authentication key.   The actual operation is not meeting this criteria.

PS: If I can get my hands on the actual entire source, I will be more than  
willing to
spent the time to zoom in on the problem.  If someone can ZIP up the  
source, that
would be the most

Thanks





-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to