Bug 131348 - canAuthenticateAgainstProtectionSpace delegate calls should not be made when ResourceHandle has credentials
Summary: canAuthenticateAgainstProtectionSpace delegate calls should not be made when ...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-07 23:28 PDT by Alexey Proskuryakov
Modified: 2014-04-07 23:28 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Proskuryakov 2014-04-07 23:28:25 PDT 
When ResourceHandle already has credentials provided via XMLHttpRequest argument or a URL, it shouldn't ask make a canAuthenticateAgainstProtectionSpace delegate call. If the client doesn't implement UI for password authentication, and thus returns false, CFNetwork won't call didReceiveAuthenticationChallenge, so we won't use the existing credentials.

We should only go ask the client if the existing credentials turned out to be incorrect.