Closed Bug 338962 Opened 19 years ago Closed 12 years ago

IPV6 raw addresses are not being accepted correctly.

Categories

(Toolkit Graveyard :: Plugin Finder Service, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: sailaja, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Build Identifier: Mozilla/5.0 When installing a Windows plugin using IPV6 address the 'allow website' display does not add IPv6 (raw) address correctly. If the website is say 2002:92a:8f7a:20:9:42:81:231 only 2002 is added to the list of acceptable websites. Reproducible: Always Steps to Reproduce: 1.Select 'Install plugin Manually' button 2.User is prompted to allow website where the plugin resides 3.Select accept button for site URL = 2002:92a:8f7a:20:9:42:81:231. Actual Results: Of the site address 2002:92a:8f7a:20:9:42:81:231 only 2002 is picked. The site is never accepted and the User is repeatedly prompted to accept the web site. Expected Results: Site 2002:92a:8f7a:20:9:42:81:231 is placed in the list of accepted website and Mozilla completes the manual install of the plugin.
Firefox -> Plugin Finder Service
Component: Installer → Plugin Finder Service
QA Contact: installer → plugin.finder
you talking about installing extensions? PFS has no "Install plugin Manually" button.
Reporter: Is there a example page where one can see this plugin (IPv4 if possible :)? doron: Probly the Reporter meant the "Manual Install" button which appears when the plugin cannot be found on the pfs server or the installation fails. Maybe the plugin he is trying to install is a XPI file (hence the allow website to install dialog)?
Sounds like someone is hand-parsing URL strings.
Flags: blocking-firefox3?
I'd block on this if someone can at least provide a testcase. Doron, can you track down the reporter via internal means?
Until this is confirmed, we can't block on it. Clearing flag, please see if we can get a confirmation (reporter? doron?) and feel free to renom.
Flags: blocking-firefox3?
Blocks: IPv6
What about creating a bug on the bugzilla landfill server and attaching an xpi? http://[2620:0:330:21:20c:29ff:fe3d:4e52]/ http://landfill.ip6.bugzilla.org/ http://landfill.ip4.bugzilla.org/ http://landfill.bugzilla.org/ (all point to the same server, just different dns configuration)
Product: Firefox → Toolkit
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.