EXPECT_TRUE(result_catcher.GetNextResult());
Verified this fails without the fix.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Devlin for the general approach from an extensions perspective.
Will find a services/network owner after.
Kelvin, JFYI.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
LGTM % nits; thanks, Andrea!
setTimeout(() => {
why async? (Add a comment)
chrome.test.sendMessage('ready');)";
as flagged elsewhere, we _shouldn't_ generally need these, if the extension isn't doing any async setup work.
EXPECT_TRUE(result_catcher.GetNextResult());
Verified this fails without the fix.
Presumably, the failure is just a timeout? (That's fine; just confirming)
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Commit-Queue | +1 |
Devlin for the general approach from an extensions perspective.
Will find a services/network owner after.Kelvin, JFYI.
Done
why async? (Add a comment)
Actually it doesn't necessarily have to be async.
as flagged elsewhere, we _shouldn't_ generally need these, if the extension isn't doing any async setup work.
Yes, I think it should be fine for this test (but apparently not **every** test...).
EXPECT_TRUE(result_catcher.GetNextResult());
Devlin CroninVerified this fails without the fix.
Presumably, the failure is just a timeout? (That's fine; just confirming)
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[Extensions] Propagate request_id to CORS preflights for proxy auth
The `webRequest.onAuthRequired` event is not firing for extensions
handling proxy authentication (HTTP 407) on CORS preflight requests.
This is because the preflight's URLLoader is created with a default
`request_id` of 0, which the WebRequest API could not associate with
the original request being proxied by the extension.
This change fixes the issue by propagating the `request_id` from the
original `CorsURLLoader` down to the `SimpleURLLoader` used for the
preflight request. This ensures the preflight and the main request are
treated as a single transaction, allowing the extension to correctly
handle the authentication challenge.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |