Opened 7 years ago

Closed 7 years ago

#8277 closed defect (fixed)

failed to get DOMWin for ... spammed to the console

Reported by: cypherpunks Owned by: pde
Priority: Low Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords: SSL Observatory spam console
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm runnning Firefox 18.0.2 on Ubuntu 12.04LTS-64bits.

When I use sabnzb, I can see sometimes, on the console where sabnzdb is launched (sabnzd launches firefox when it starts), a lot of spam from httpseverywhere, linked to the SSL Observartory.

I have outputs like:

failed to get DOMWin for https://trac.torproject.org/tor.css

failed to get DOMWin for https://trac.torproject.org/projects/tor/chrome/common/css/ticket.css

failed to get DOMWin for https://blahblahblah....

SSL Observatory: Cert submission failure 0:

It does not seem to disrupt Firefox, but I'm not sure the observatory really works as it report a failure (but usually... at least on Linux, a return code of 0 would mean all OK and not a failure, so the message is very unclear).

I'm quite annoyed anyway to be spammed in the console, although it might be a side effect as firefox has been launched from the command line (due to launching it through sabnzb)

Child Tickets

Change History (1)

comment:1 Changed 7 years ago by pde

Resolution: fixed
Status: newclosed

Hi sabnzd,

the "failed to get DOMWin" messages are indeed too verbose, and I'll make those silent by default in future.

the observatory messages were real results of the server being down, so those are semi-important.

In any case, if you want to completely silence HTTPS Everywhere, you can go into about:config, search for the "loglevel" variable, and set it to 6.

Note: See TracTickets for help on using tickets.