Compatibility with pseudo-protocols (like private:) from other extensions
See original GitHub issueThe Private Tab Firefox extension lets users open private tabs in the same window as normal tabs.
If you type private:https://www.example.com/
into the address bar or use it as a bookmark, the tab will automatically be converted to a private one, and the private:
preffix will be dropped during the process.
I’m trying to create Redirector rules to add private:
before some URLs automatically (along with an extra string to prevent loops), but can’t get it to work. This is what I have so far:
Is there a way to make it work with the current version of Redirector? Maybe you can fix it by taking a look at the Private Tab API.
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Design Considerations for Protocol Extensions RFC 6709
Otherwise, when two "private" or "experimental" extensions encounter each other on a public network, unexpected interoperability problems ...
Read more >Scalable Private Set Intersection Based on OT Extension
Abstract. Private set intersection (PSI) allows two parties to compute the intersection of their sets without.
Read more >The Transport Layer Security (TLS) Protocol Version 1.2
The keys for this symmetric encryption are generated uniquely for each connection and are based on a secret negotiated by another protocol (such...
Read more >mod_ssl - Apache HTTP Server Version 2.4
For backward compatibility the information can be made available under different names, too. ... This is similar to the SSLRequireSSL directive. Require ssl ......
Read more >Networking 101: Transport Layer Security (TLS)
As part of the TLS handshake, the protocol also allows both peers to ... new protocols and extensions to HTTP, such as WebSocket,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Gitoffthelawn @yfdyh000
Now there’s a way to always automatically open specific domains in private tabs/containers: https://addons.mozilla.org/addon/temporary-containers/ (disable the “automatic mode” setting).
There’s also an extension to keep your history clean of unwanted URL patterns: https://addons.mozilla.org/addon/historia/ . It accepts simple expressions and regex rules like these:
It’s a nice idea, but not something I’m interested in adding to Redirector. I think this might be a better feature request for the PrivateTab extension itself, to have a list of regexes for urls that should always open in private tabs.