Determine how to deal with nested URIs

[myrdd]

Technically, so-called „nested URIs“ are URIs that implement the nsINestedURI interface.
Like any other (normal) URI they also implement the nsIURI interface.

An example for a nested URI is view-source:https://github.com:

• view-source is the scheme
• https://github.com is the path – and at the same time the inner URI.

There are two issues about such nested URIs:

1. How should RPC handle them regarding allowing or blocking?
2. How should such URIs be displayed in the menu?

---

About (1), in case of the example above, we probably want to extract the "real URL" and check if that should be allowed or blocked.
This is what RPC already does, but only for the view-source scheme (see here). There is a pull request about jars, see #409.

Again about (1) – what should RPC do in general? One option I could think of is that RPC always checks if the URI is nested and then takes the innermost URI to check for rules that match it.

---

About (2) – how to show such URIs in the menu – I don't have any plan yet.