FoxyProxy Basic のレビュー
FoxyProxy Basic 作成者: Eric Jung、 erosman
Abdussamad によるレビュー
5 段階中 4 の評価
Abdussamad によるレビュー (7年前)It's very good. It would be even better if two features could be added. The ability to quickly change proxies with a single click on the toolbar button. Perhaps left clicking or middle clicking there would cycle through the proxies. A keyboard shortcut would be a bonus.
Another feature which was alluded to by Tristan Gallet is the ability to add exceptions i.e. a blacklist of IPs that are not proxied. This is offered in the default firefox implementation of proxying too. For example the ability to configure it so that connections to 127.0.0.1 or your router IP address are not proxied.
Apart from that it's great. Thanks for rewriting it for FF Quantum!
Another feature which was alluded to by Tristan Gallet is the ability to add exceptions i.e. a blacklist of IPs that are not proxied. This is offered in the default firefox implementation of proxying too. For example the ability to configure it so that connections to 127.0.0.1 or your router IP address are not proxied.
Apart from that it's great. Thanks for rewriting it for FF Quantum!
合計レビュー数: 79
- 5 段階中 5 の評価Firefox ユーザー 18204588 によるレビュー (1年前)
開発者の返信
投稿日時: 1年前Due to the code unification, ATM they are the same but in future, pattern related features will become hidden. Users can still share settings between Basic & Standard, and Chrome & Firefox.- 5 段階中 5 の評価Firefox ユーザー 17831150 によるレビュー (2年前)
- 5 段階中 1 の評価Firefox ユーザー 10917032 によるレビュー (2年前)
- 5 段階中 5 の評価random2222 によるレビュー (3年前)
- 5 段階中 5 の評価Firefox ユーザー 17120376 によるレビュー (3年前)
- 5 段階中 5 の評価Firefox ユーザー 16507014 によるレビュー (4年前)
- 5 段階中 5 の評価Firefox ユーザー 16460979 によるレビュー (4年前)
- edit: seems to be a bug in Firefox, not FoxyProxy, other proxy extensions have the same issue. glad for a prompt response from developer
When a SOCKS5 proxy is enabled, if DNS over HTTPS in Firefox is turned on, Firefox does not seem to respect if the proxy server handles DNS or not; it will still query DNS through Cloudflare or NextDNS or whatever it's set to in the browser settings, potentially leaking DNS information