802065 - DNS cache is not cleared while switching to SOCKS proxy

Status: UNCONFIRMED

(Core :: Networking, defect, P5)

Description

[Aymeric Vitte]

User Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

network.proxy.socks_remote_dns is true

No proxy is defined, from the web console try :

document.body.innerHTML='<iframe src="http://abcdefg.com" width="100%" height="100%" />'

The domain is resolved to hookedonphonics.com and a GET request is sent to it.

Now set a socks v5 proxy and do the same.

The console displays a GET to hookedonphonics.com, even if the socks proxy is not responding (this is not the subject of this bug but please note that this is surprising since the socks message in that case is indicating abcdefg.com:80), then, to make sure, looking at the messages with a working socks proxy we can see :

2 socks requests toward abcdefg.com:80 followed by 1 socks request toward hookedonphonics.com:80 and then a GET request toward hookedonphonics.com since it responded first

Clear the cache and do the same, there is no more socks requests toward hookedonphonics.com, socks requests are followed by a GET request toward abcdefg.com





Expected results:

After setting the socks proxy, the socks requests should not indicate hookedonphonics.com as the destination but abcdefg.com only. In addition the behavior seems strange since socks requests are sent toward both after switching to the socks proxy without clearing the cache.

If required I can provide the log files with the messages but they are huge and not very easy to read.

Comment 1

[Patrick McManus [:mcmanus]]

dup of 652928 - you can confirm with a nightly or aurora build?

Comment 2

[Aymeric Vitte]

Attachment: log file node-Tor

Comment 3

[Aymeric Vitte]

I don't think it's a duplicate of bug 652928

I tried with the latest nightly build and the problem is still there.

Please see the log file (coming from https://github.com/Ayms/node-Tor ) and seek for 'INCOMING SOCKET', you will see that FF sends abcdefg.com:80 and hookedonphonics.com:80

Comment 4

[Patrick McManus [:mcmanus]]

thanks for the followup

Comment 5

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 6

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 7

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.