Closed
Bug 1066602
Opened 12 years ago
Closed 12 years ago
labs.mozilla.org over HTTPS asking for LDAP
Categories
(Infrastructure & Operations Graveyard :: WebOps: Labs, task)
Infrastructure & Operations Graveyard
WebOps: Labs
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pmac, Assigned: gozer)
Details
(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/1268] )
Going to http://labs.mozilla.org redirects to https://mozillalabs.com as expected. But going to the HTTPS version (https://labs.mozilla.org) gives an SSL Cert error due to a name mismatch. If you accept this exception and continue it will prompt you for LDAP credentials via HTTP Basic Auth. Expected behavior is that it should redirect to labs.m.o like the insecure version.
| Assignee | ||
Comment 1•12 years ago
|
||
(In reply to Paul McLanahan [:pmac] from comment #0)
> Going to http://labs.mozilla.org redirects to https://mozillalabs.com as
> expected. But going to the HTTPS version (https://labs.mozilla.org) gives an
> SSL Cert error due to a name mismatch. If you accept this exception and
> continue it will prompt you for LDAP credentials via HTTP Basic Auth.
> Expected behavior is that it should redirect to labs.m.o like the insecure
> version.
How did you come about this issue? Did you run into an existing link for https://labs.mozilla.org/?
I am asking because labs.mozilla.org was originally setup as http-only, so this doens't seem to be
a regression, trying to understand impact here.
| Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Philippe M. Chiasson (:gozer) from comment #1)
> How did you come about this issue? Did you run into an existing link for
> https://labs.mozilla.org/?
IRC user "ko_lo" in #www this morning notified us. I've no idea where they might have found it. What they said was: "I tried to reach mozilla labs, my first try was labs.mozilla.org but I got a wrong https cert (bad domain), I ignore the warning and I was asked for my ldap passwd".
Hi there,
(In reply to Paul McLanahan [:pmac] from comment #2)
> IRC user "ko_lo" in #www this morning notified us. I've no idea where they
> might have found it.
labs.m.o was a "lucky" try, I remember a mail/xpi dealing with this domain so I tried.
to be honnest I think the impact is very very low.
| Assignee | ||
Comment 4•12 years ago
|
||
(In reply to ko_lo from comment #3)
> Hi there,
>
> (In reply to Paul McLanahan [:pmac] from comment #2)
> > IRC user "ko_lo" in #www this morning notified us. I've no idea where they
> > might have found it.
>
> labs.m.o was a "lucky" try, I remember a mail/xpi dealing with this domain
> so I tried.
> to be honnest I think the impact is very very low.
In that case, we are going to leave this as-is.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Comment 5•12 years ago
|
||
Interesting timing, I *just* altered this a day or two ago over in bug 756228. Specifically, it no longer listens on port 443. That was a configuration error. There is no cert for this on the load balancer (hence the cert error) and the backend servers don't listen on port 81 (hence falling through to the alphabetically first site that does, which happens to require LDAP).
The primary reason for this change is so folks with things like HTTPS Everywhere don't get bit by incorrect certs or invalid configs.
Updated•10 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•