Thanks for the investigation Rob! I think what's happening here is that AC looks at the `jar:` URI and thinks it's something the browser cannot load and then try to send it to an external app, although now I'm wondering if this is the right behavior? I thought we only did that for very specific types of URIs? This sounds like it might be problematic. :csadilek do you have opinions about this ^ ? As to fix this we should probably send the `moz-extension` URI instead of the `jar` URI in `onLoadRequest.
Bug 1685403 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for the investigation Rob! I think what's happening here is that AC looks at the `jar:` URI and thinks it's something the browser cannot load and then tries to send it to an external app, although now I'm wondering if this is the right behavior? I thought we only did that for very specific types of URIs? This sounds like it might be problematic. :csadilek do you have opinions about this ^ ? As to fix this we should probably send the `moz-extension` URI instead of the `jar` URI in `onLoadRequest.
Thanks for the investigation Rob! I think what's happening here is that AC looks at the `jar:` URI and thinks it's something the browser cannot load and then tries to send it to an external app, although now I'm wondering if this is the right behavior? I thought we only did that for very specific types of URIs? This sounds like it might be problematic. :csadilek do you have opinions about this ^ ? As to fix this we should probably send the `moz-extension` URI instead of the `jar` URI in `onLoadRequest`.