DNR redirect rules won’t redirect to extension paths

[lenacohen]

DNR rules redirecting to an extension path lead to an error page: “Safari can’t open the page. The error is: “The operation couldn’t be completed. (NSURLErrorDomain error -1008.)” (NSURLErrorDomain:-1,008).”

This is an example of a redirect rule that leads to an error page instead of the extension path page:

chrome.declarativeNetRequest.updateDynamicRules({addRules: [
    {
        id: 2,
        priority: 1,
        action: {
          type: "redirect",
          redirect: {
            extensionPath: "/web_accessible_resources/test_redirect.html"
          }
        },
        condition: {
            urlFilter: "||washingtonpost.com^",
            resourceTypes: [
                "main_frame"
            ]
        }
      }
]});

The extension path is included in web_accessible_resources in the extension manifest:

      "web_accessible_resources": [{
        "resources": [
          "web_accessible_resources/test_redirect.html"
        ],

Demo Xcode extension: https://github.com/lenacohen/Safari-Test-Extensions/tree/main/dnr-extension-path-redirect (test by navigating to www.eff.org and www.washingtonpost.com)
Apple Feedback Assistant Bug Report: FB16607632
Apple Developer Forum Post
Safari version 18.3
MacOS Sequoia 15.3.1

[lenacohen]

Still an issue when I tested on Safari Technology Preview Release 215

[ghostwords]

This is an important issue to fix for Privacy Badger as it breaks our "surrogate" scripts, which is important for reducing site breakages. It also breaks advanced surrogate API click-to-activate widget replacements, like the ones for Twitter and YouTube APIs.