Closed
Bug 1430568
Opened 7 years ago
Closed 7 years ago
certificate issue on publicsuffix.org.
Categories
(Infrastructure & Operations :: SSL Certificates, task)
Infrastructure & Operations
SSL Certificates
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 134402
People
(Reporter: rctgamer3, Assigned: sidler)
References
()
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/6062])
https://publicsuffix.org./ isn't accessible - uses a wrong certificate (SSL_ERROR_BAD_CERT_DOMAIN) or isn't redirected to the dotless version properly.
|
||
Updated•7 years ago
|
Assignee: nobody → server-ops-webops
Component: Other → WebOps: SSL and Domain Names
Product: Websites → Infrastructure & Operations
QA Contact: smani
Version: Development → unspecified
|
||
Comment 1•7 years ago
|
||
Thank you for reporting this to us. We're bringing this into our sprint to investigate. In the meantime, it should function normally as long as the trailing dot is excluded.
|
Assignee | |
Comment 2•7 years ago
|
||
I can confirm that this happens on Chrome and Safari browsers but not Firefox. I also tried this on https://github.com and found that it just works or is redirected without the trailing '.'. I am going to ask atoll about this and see what he thinks.
This is a Firefox product concern and not a site operator concern (no one can fix this, regardless of who the site operator is, due to the CN/SAN definitions).
Bug 134402 has been open for 16 years with a clear indication of "we refuse to support this", so I do not expect it possible to change their minds on this matter.
Additionally, no certificate authorities will issue a certificate containing a trailing '.' as they are not a valid part of the commonName or serverAltNames properties.
Per our standing guidance in bug 134402, please do not use a trailing '.' when constructing URLs.
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.
Description
•