Closed
Bug 1796278
Opened 1 year ago
Closed 1 year ago
AAAA records are confused for a domain within a container
Categories
(Core :: Networking: DNS, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1420777
People
(Reporter: g00g1, Unassigned, NeedInfo)
Details
Attachments
(1 file)
2.05 MB,
video/mp4
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0
Steps to reproduce:
- create new container
- open encryp.ch (it's AAAA is 2a0c:b641:6f1:55:656e:6372:726f:6f74)
- open new tab within the same container
- open git.encryp.ch (it's AAAA is 2a0c:b641:6f1:55:6769:7465:6e63:7200)
- firefox thinks that git.encryp.ch has IPv6 address 2a0c:b641:6f1:55:656e:6372:726f:6f74
Actual results:
IPv6 address of git.encryp.ch was consufed with encryp.ch one
Expected results:
Each (sub) domain have it's own IPv6
Updated•1 year ago
|
Component: Untriaged → Networking: DNS
OS: Unspecified → Linux
Product: Firefox → Core
Hardware: Unspecified → x86_64
Comment 1•1 year ago
|
||
This seems a lot like bug 1420777.
We want to fix it soon. The gist of it is if one domain returns a cert valid for the other, and there's an overlap in the DNS records of the domains, then they will be coalesced.
If that's not the case for you please let me know.
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: http2-connection-coalescing
Flags: needinfo?(me)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•