Cari Bantuan

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Pelajari Lebih Lanjut

nytimes.com no longer works on firefox 23 !!? what's the option in the browser to disable "Mixed Content" ? Thank you!

  • 4 balas
  • 5 memiliki masalah ini
  • 4 kunjungan
  • Balasan terakhir oleh frans tenggara

more options

nytimes.com no longer works on firefox 23 !!? what's the option in the browser to disable "Mixed Content" ? Thank you! edit

Below is the error message I get. Note though that the same url (www.nytimes.com works perfectly in I.E. & Chrome).


Network Error (tcp_error)

A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

For assistance, contact your network support team.

nytimes.com no longer works on firefox 23 !!? what's the option in the browser to disable "Mixed Content" ? Thank you! edit Below is the error message I get. Note though that the same url (www.nytimes.com works perfectly in I.E. & Chrome). Network Error (tcp_error) A communication error occurred: "" The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time. For assistance, contact your network support team.

Semua Balasan (4)

more options

Yes, that is a known issue.

  1. In the Location bar, type about:config and press Enter. The about:config "This might void your warranty!" warning page may appear.
  2. Click I'll be careful, I promise!, to continue to the about:config page.
  3. Enter security.mixed_content.block_active_content in the filter.
  4. Double click it and it should turn bold, and say false.
  5. Refresh New York Times and if needed restart firefox.
more options
more options

The problem exists with https://www.nytimes.com/ so, as a workaround, you can use http://www.nytimes.com/ (not https) or http://nytimes.com where I don't see the problem.

Related bug report, if anyone wants to keep track, so that they can reset the security.mixed_content.block_active_content preference, when it's fixed (read Bugzilla Etiquette before commenting in bug reports):

  • Bug 862164 - https://www.nytimes.com/ does not render properly because of mixed content blocking
more options

type about:config then type: security.mixed_content.block_active_content in the filter bar and choose false. its work for me