X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Why do you tell your customers that the website owner has set up their website improperly when in reality, the owner has chosen not to purchase an SSL Cert?

Kuphostiwe

Just because a website doesn't have an https:// designation, does not mean the owner has set up their site improperly. Thanks so much for throwing me and other website owners under the bus for your policies.

I suggest you change the language.

Just because a website doesn't have an https:// designation, does not mean the owner has set up their site improperly. Thanks so much for throwing me and other website owners under the bus for your policies. I suggest you change the language.

Eminye Imininingwane Yohlelo

Fakela amapulagi

  • Shockwave Flash 29.0 r0

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0

Eminye Imininingwane

WestEnd 60 izisombululo 5387 izimpendulo
Kuphostiwe

Links? FF doesn't change language that is up to the site itself.

Links? FF doesn't change language that is up to the site itself.
jscher2000
  • Top 10 Contributor
8838 izisombululo 72239 izimpendulo
Kuphostiwe

Impendulo Ewusizo

Hi legere864, you're right that this may not be the webmaster's fault. The error may occur if:

  • The user is using HTTPS Everywhere or another extension that "upgrades" from HTTP to HTTPS.
  • The user has security software or malware operating as a "man in the middle" of the connection.

The current text is defined as follows:

certerror.introPara "The owner of <span class='hostname'/> has configured their website improperly. To protect your information from being stolen, &brandShortName; has not connected to this website."

Probably what the error should say is something more along the lines of:

"&brandShortName; received a web server certificate that either did not match <span class='hostname'/> or could not be verified as valid. To protect your information from being stolen, &brandShortName; has not connected to this website."

But that might be too technical for some users.

Do you want to file a bug suggesting a specific wording change? Because Firefox error messages need to be translated in numerous languages, this kind of thing won't happen quickly, but you could at least get the ball rolling.

And meanwhile, many hosts now offer free HTTPS, and Google is said to give higher rank to HTTPS sites, so please see whether you can get it for your site(s).

Hi legere864, you're right that this may not be the webmaster's fault. The error may occur if: * The user is using HTTPS Everywhere or another extension that "upgrades" from HTTP to HTTPS. * The user has security software or malware operating as a "man in the middle" of the connection. The current text is defined as follows: certerror.introPara "The owner of &lt;span class='hostname'/&gt; has configured their website improperly. To protect your information from being stolen, &brandShortName; has not connected to this website." Probably what the error should say is something more along the lines of: "&brandShortName; received a web server certificate that either did not match &lt;span class='hostname'/&gt; or could not be verified as valid. To protect your information from being stolen, &brandShortName; has not connected to this website." But that might be too technical for some users. Do you want to file a bug suggesting a specific wording change? Because Firefox error messages need to be translated in numerous languages, this kind of thing won't happen quickly, but you could at least get the ball rolling. * https://bugzilla.mozilla.org/enter_bug.cgi * https://developer.mozilla.org/docs/Mozilla/QA/Bug_writing_guidelines And meanwhile, many hosts now offer free HTTPS, and Google is said to give higher rank to HTTPS sites, so please see whether you can get it for your site(s).

Okulungisiwe ngu jscher2000