<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/01/2013 03:36 PM, Claudio Moretti
wrote:<br>
</div>
<blockquote
cite="mid:CAMw1ynRWBGoWa+b+p893_RXDzsJGF6RSMkc5+SX67O0QRYsR7Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Thu, Aug 1, 2013 at 11:54 PM, Dan
Auerbach <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:dan@eff.org" target="_blank">dan@eff.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi Claudio,<br>
<br>
We are listening on 80 but there's no content -- just
that default page -- but it can be used to test
whether the host is up. If you go to <a
moz-do-not-send="true"
href="https://observatory.eff.org" target="_blank">https://observatory.eff.org</a>,
you can test if the SSL connection is working. If you
submit a cert, you can test if submitting a cert works
:)<br>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Hi Dan,<br>
</div>
<div><br>
</div>
<div>Yeah, I should've thought about that. The SSL
connection works for me; stupid question, though: how can
I force (and log) sending a certificate? (RTFM is an
accepted and welcome response, pinky swear)<br>
<br>
</div>
<div>Claudio<br>
</div>
</div>
</div>
</div>
</blockquote>
There's a client side whitelist of very popular certs that do not
get submitted, and also a list of certs you've already submitted.
Visit an obscure site with SSL that you haven't visited before, and
that should work. Or fiddle with <a class="moz-txt-link-freetext" href="about:config">about:config</a> settings (search for
"observatory") to turn off the client side whitelist and the caching
of submitted certs, then visit any website with SSL and it should do
a submission.<br>
<br>
Cheers,<br>
Dan<br>
</body>
</html>