[Webkit-unassigned] [Bug 80713] Add new methods to FrameLoaderClient so different WebKit ports can customize the ResourceRequest when it is created.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Apr 19 15:49:49 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=80713


Nate Chapin <japhet at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #131621|review?                     |review-
               Flag|                            |




--- Comment #53 from Nate Chapin <japhet at chromium.org>  2012-04-19 15:49:47 PST ---
(From update of attachment 131621)
I'm inclined to agree with ap that adding these new callbacks is not the right answer, especially for the subresource case. 

Since we don't do policy checks for subresources, dispatchWillSendRequest() seem like the right time for them. For the policy checks for main resource, perhaps we can approximate the TargetType, especially since there should be only 2 possibilities, then just set the real TargetType in dispatchWillSendRequest() as well?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list