Closed Bug 606900 Opened 14 years ago Closed 10 years ago

Error de redireccionamiento con el .com

Categories

(Firefox :: General, defect)

3.6 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cristian56, Unassigned, NeedInfo)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8

Para poder soportar la redirección de .com, me tengo que ir a about:config y escribir una nueva entrada de tipo lógico a true, que se llame network.IDN.whitelist.com, ya que no está contemplado en este estupendo navegador.

Reproducible: Didn't try

Actual Results:  
Me redirige a otra página, y me muestra en la barra de direcciones la otra dirección, y no la correcta.
network.IDN.whitelist.com has nothing to do with redirection, but with the IDN display (non-ASCII characters in the domainname).

I think you want to complain that you can't see non-ASCII characters in a .com domainname. That's actually on purpose, since the .com top level domain is not safe to use, as it doesn't provide protection against homographic attacks. Firefox has a list of top level domains that are safe to use, but .com isn';t part of it. See <http://www.mozilla.org/projects/security/tld-idn-policy-list.html> and <http://www.chromium.org/developers/design-documents/idn-in-google-chrome>

But that shouldn't have any influence on any redirection at all, only on the actual display in the locationbar.
Version: unspecified → 3.6 Branch
Cristian please use English as it's the official language in bugzilla. I tried to reproduce this issue on the 12/23 Nightly, but I see no redirect.

Cristian, por favor utilize ingles en Bugzilla porque este es la lengua official aqui. Trate de reproducir este problema, pero no veo ningun redireccion. Quando deberia ver eso?
Flags: needinfo?(cristian56)
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.