Closed Bug 474824 Opened 16 years ago Closed 7 years ago

Firefox socks system proxy configuration broken w/ socks_remote_dns

Categories

(Core :: Networking, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 562289

People

(Reporter: me, Assigned: xeonchen)

References

Details

(Keywords: privacy, Whiteboard: [necko-active][proxy])

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5 socks_remote_dns does not work with Firefox's automagic system-proxy detection. You will have to hard code the socks5 proxy into Firefox's connection dialog to use socks_remote_dns. Reproducible: Always Steps to Reproduce: 1.Set up a sock5 proxy in gnome-network-preferences 2.Set Firefox to "Use System Proxy Settings" (Preferences -> Advanced -> Network -> Settings) 2.Set network.proxy.socks_remote_dns to true Actual Results: DNS is not tunneled through socks5. Expected Results: DNS to be tunneled through socks5. Tested and verified on Linux using gnome.
Version: unspecified → 3.1 Branch
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Version: 3.1 Branch → unspecified
I've encountered this bug as well.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: privacy
Summary: Firefox Network proxy detection no workie w/ socks_remote_dns → Firefox socks system proxy configuration broken w/ socks_remote_dns
What this bug still has not been resolved?
Whiteboard: [necko-backlog]
Whiteboard: [necko-backlog] → [necko-backlog][proxy]
Does anyone still experience this issue? If yes, please provide your version information and it would be great to provide the HTTP log[1] for analysis. Thank you. https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging
Assignee: nobody → xeonchen
Whiteboard: [necko-backlog][proxy] → [necko-active][proxy]
I cannot reproduce this and I think this has been fixed by bug 562289.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.