X
Thinta lapha ukuze uye kuveshini yamakhalekhukhwini kusayithi.

Isithangami Sabeseki

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

Incorrectly displays the domain name protected by the SSL certificate

Kuphostiwe

Firefox incorrectly displays the domain name protected by the SSL certificate. Namely, if the name has escaped characters, then they are displayed.

I attach a screenshot. https://i.paste.pics/68eddeae26ebdc356b46e73ca924e13c.png

In other browsers there is no such problem.

For example: https://www.indeks.ru

Firefox incorrectly displays the domain name protected by the SSL certificate. Namely, if the name has escaped characters, then they are displayed. I attach a screenshot. https://i.paste.pics/68eddeae26ebdc356b46e73ca924e13c.png In other browsers there is no such problem. For example: https://www.indeks.ru

Eminye Imininingwane Yohlelo

Isisebenziso

  • I-ejenti Engumsebenzisi: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36

Eminye Imininingwane

FredMcD
  • Top 10 Contributor
4254 izisombululo 59572 izimpendulo
Kuphostiwe

I get the same thing. The website may be using non-standard characters in its name.

I get the same thing. The website may be using non-standard characters in its name.

Umnikazi wombuzo

In other browsers (IE, CHROME, OPERA) there is no such problem.

In other browsers (IE, CHROME, OPERA) there is no such problem.

Umnikazi wombuzo

Tell me, please, how is it possible to solve this problem?

Tell me, please, how is it possible to solve this problem?
FFus3r 50 izisombululo 757 izimpendulo
Kuphostiwe

your browser is in russian language.

your browser is in russian language.

Umnikazi wombuzo

And how will this information help with the solution of this issue?

And how will this information help with the solution of this issue?
FredMcD
  • Top 10 Contributor
4254 izisombululo 59572 izimpendulo
Kuphostiwe

Have you checked with the website support on this? Can you post a picture of how other browsers show that site?

Have you checked with the website support on this? Can you post a picture of how other browsers show that site?

Umnikazi wombuzo

I attach a screenshot.

I attach a screenshot.
FredMcD
  • Top 10 Contributor
4254 izisombululo 59572 izimpendulo
Kuphostiwe

Your snapshot shows the same problem on all browsers. Do you see the three zeros?

Your snapshot shows the same problem on all browsers. Do you see the three zeros?

Umnikazi wombuzo

This is not three zeros. These are the three Russian letters "O". And this has nothing to do with this issue. The problem is that Mozilla displays a slash slash next to the quotes. And in other browsers there is no such problem. Do you see slashes (\) before the quotes?

This is not three zeros. These are the three Russian letters "O". And this has nothing to do with this issue. The problem is that Mozilla displays a slash slash next to the quotes. And in other browsers there is no such problem. Do you see slashes (\) before the quotes?
FredMcD
  • Top 10 Contributor
4254 izisombululo 59572 izimpendulo
Kuphostiwe

I called for more help.

I called for more help.
cor-el
  • Top 10 Contributor
  • Moderator
17516 izisombululo 158398 izimpendulo
Kuphostiwe

We had another question about a similar issue, so it seems the current Firefox releases still do not handle escaped quotes in certificate records.

We had another question about a similar issue, so it seems the current Firefox releases still do not handle escaped quotes in certificate records. *[/questions/1218275] Discrepancy in SSL certificate owner for: https://www.t-mash.ru. Blink/WebKit: O="Tekhnologii i Mashiny" LLC; Gecko: O=\"Tekhnologii i Mashiny\" LLC?

Umnikazi wombuzo

Yes, this is a similar problem. Thus, Mozilla Firefox has a problem with displaying escaped quotes in certificate records. How and when does Mozilla Firefoch plan to solve this problem?

Yes, this is a similar problem. Thus, Mozilla Firefox has a problem with displaying escaped quotes in certificate records. How and when does Mozilla Firefoch plan to solve this problem?