Clients using the async methods like willSendRequestAsync or didReceiveResponseAsync use a method to continue like continueWillSendRequest or continueDidReceiveResponse. We are not implementing those yet, even though nwe are calling the async methods. In the case of willSendRequest it's clear we need to implement continueWillSendRequest because the request might have changed, but in the other cases we still don't know whether they are required or not.
Found a use case where continueDidReceiveResponse is required, when the main resource load is converted into a download by the policy checker. Patch attached to bug #126131 implements continueDidReceiveResponse.
continueWillSendRequest() is now implemented too, so I'm renaming the bug.
My fix for bug 132308 (r168232) removed the continueShouldUseCredentialStorage() call. I think there's anything more to do in this bug now.
(In reply to comment #3)
> I think there's anything more to do in this bug now.
I mean.. I don't think there's anything more to do in this bug now.