@tasket@infosec.exchange @julian with http: and https: the pattern is not to use a protocol handler but to instead use a content-type handler. a different protocol forks the network, and leads to bad UX when you have custom protocol links being copied into apps that don't understand them. also you end up with multiple links for the same thing, and you have to recognize equivalences wherever there might be any.web links have a "type" parameter for this. see firefox for example (pic 1) on SVG or PDF content
F
