Closed Bug 1680253 Opened 2 years ago Closed 2 years ago

Firefox didn't use ips shown in "about:netowrk#dns" to connect to website

Categories

(Core :: Networking, defect)

Firefox 83
Desktop
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1420777

People

(Reporter: ovearj, Unassigned)

Details

Attachments

(1 file)

146.10 KB, application/x-zip-compressed
Details
Attached file screenhosts-taobao.zip

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Steps to reproduce:

1)Install firefox 83.0 stable or firefox nightly
2)open www.taobao.com
3)click "我的淘宝"

about:networking#dns shows (attached screenshots)

www.taobao.com ipv4 false
113.96.109.100
113.96.109.101
::

i.taobao.com ipv4 false
203.119.144.26
::

Actual results:

Firefox use 113.96.109.100 to connect "i.taobao.com" which belongs to "www.taobao.com" (see attachments)
Page can not load properly.

Expected results:

Firefox use 203.119.144.26 to connect "i.taobao.com".
Page load without any problem.

Addition information
1.Not work on new profile either
2.Firefox nightly still have this problem.
3.Tried with another computer with fresh windows&firefox installation, but still not work.
4.Other browsers work without any problem.

Hello I have tried to reproduce the issue with the STR provided in the description but unfortunately I wasn't able to do so using Firefox 83.0 with Windows 10 64-bit. I will set a component for this issue in order for one of our developers could look more into it. If it's not the right component please feel free to change it to an appropriate one.

Component: Untriaged → Networking
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → Desktop
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE

Hi Reporter,

Could you try to get the http log? Just want to confirm if this is really a connection coalescing bug.

Thanks.

Flags: needinfo?(ovearj)

This is actually a dup of bug 1680249.

Flags: needinfo?(ovearj)
You need to log in before you can comment on or make changes to this bug.