A protocol shouldn't be specifying the client software in the first place. That's sort of the entire point of a protocol, that it can be implemented in multipl

A protocol shouldn't be specifying the client software in the first place. That's sort of the entire point of a protocol, that it can be implemented in multiple different clients. So to answer your question, yes. If a program is specifying "firefox://" and using it to mean "https:// https://", then that should be considered a bug in the program specifying it. That bug can either be fixed in the program itself, or can have a workaround in an external program.