Beoardielingen foar FoxyProxy Standard
FoxyProxy Standard troch Eric Jung
Wurdearringen foar Eric
Wurdearring: 2 fan 5
troch Eric, 2 jierren lynIt's getting worse and worse. I didn't like at all the current presentation/way to work compared to previous versions, and now the "Proxy by pattern" option has disappeared when I click on the extension, I have only "Disable" or my proxy to select, and the patterns don't work of course, they worked only when "Proxy by pattern" was enabled. Edit since I cannot reply to the answer below: I do have patterns there associated to my socks server, I've been using them for a long time, it's just that the menu entry "Proxy by pattern" has suddenly disappeared.... Only full proxy or disabled are still available. Is there a support forum where I could put screenshots?
Antwurd ûntwikkeler
2 jierren lyn pleatst"Proxy by Patterns" wont appear if user doesn't have any patterns. Obviously, once user adds some patterns, "Proxy by Patterns" will appear too.
1.009 beoardielingen
- Wurdearring: 5 fan 5troch Firefox-brûker 20054704, 13 oeren lyn
- Wurdearring: 4 fan 5troch Alt Grey, 19 dagen lynIt do not work on the browser start for the first moments. So, the browser loads previously opened tabs without using a proxy.
- Wurdearring: 5 fan 5troch Firefox-brûker 14274837, 22 dagen lynSince I am unable to directly reply to other users' comments, I am commenting here instead.
Regarding the issue reported by some users that the extension cannot be used, it is suggested to try changing the value of the "network.proxy.type" setting in about:config. If the value is 0, you can try changing it to 1. If it is PAC, you can change it to 5. - Wurdearring: 1 fan 5troch cxtbs, ien moanne lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 18104331, ien moanne lynWorks very well and the dev responds on GitHub, which is a great extra.
- Wurdearring: 2 fan 5troch Firefox-brûker 19981530, ien moanne lyn
- Wurdearring: 3 fan 5troch daydreaming, 2 moannen lynFor almost a year now, FoxyProxy hasn’t been functioning properly. The extension keeps staying connected to the very first city that was selected during the initial setup. Even when changing the location in the settings, it still remains stuck on that original city.
The developers seriously need to investigate this issue. Me and several other users have been experiencing the same problem, and the only temporary fix seems to be uninstalling and reinstalling the extension completely. - Wurdearring: 5 fan 5troch Firefox-brûker 18586574, 2 moannen lyn
- Wurdearring: 5 fan 5troch liberty, 3 moannen lyn
- Wurdearring: 5 fan 5troch TheSketty, 3 moannen lyn
- Wurdearring: 4 fan 5troch Firefox-brûker 19822245, 3 moannen lyn
- Wurdearring: 3 fan 5troch logika, 3 moannen lyn
- Wurdearring: 4 fan 5troch Firefox-brûker 19689787, 4 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 18285082, 4 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 19438688, 5 moannen lyn
- Wurdearring: 5 fan 5troch Firefox-brûker 19734710, 5 moannen lyn
- Wurdearring: 5 fan 5troch Thomas, 6 moannen lyn
- Wurdearring: 5 fan 5troch Darias, 6 moannen lyn
- Wurdearring: 5 fan 5troch Ali3n, 7 moannen lyn