This is the exact underlying issue in bug 1147695, and I have a similar patch that fixes it.
Currently when sending a CSP report, HttpBaseChannel::ShouldIntercept tries to get access to the nsINetworkInterceptController interface through the channel's notification callbacks, but in this case the notification callback is the CSPReportRedirectSink object (thanks to nsCORSListenerProxy::Init). This patch extends CSPReportRedirectSink to make it aware of nsINetworkInterceptController, and have it route the request for nsINetworkInterceptController correctly to the docshell without the need to mess with the notification callbacks. This will be tested in bug 1147699.
Attachment #8583937 - Flags: review?(nsm.nikhil)
Attachment #8583937 - Flags: review?(nsm.nikhil) → review+
You need to log in before you can comment on or make changes to this bug.