163210 - mozdev projects don't install

Status: RESOLVED INVALID

(Core Graveyard :: Installer: XPInstall Engine, defect)

Description

[Bjarne D Mathiesen]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.1) Gecko/20020814
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.1) Gecko/20020814

When trying to install eg bannerblind & multizilla, 
-- I get a -207 error
-- am told that it's not a valid installer

I've tried to delete
-- Component Registry
-- chrome.rdf
but the issue still persists


Reproducible: Always

Steps to Reproduce:
1. got to the install page of a mozdev project eg http://multizilla.mozdev.org/
2. click on the installer

Actual Results:  
download completed but install failed with above mentioned messages

Expected Results:  
Installed the package

there's no problems installin on 1.1b
regerssion issue

Comment 1

[Bjarne D Mathiesen]

This is also an issue under Mac OS X 10.1.5 2002081416

Comment 2

[James Ogden]

I believe that this is a proxy issue, rather than a Mozilla problem.  I got this
error:

ERROR
The requested URL could not be retrieved

While trying to retrieve the URL:
http://downloads.mozdev.org/multizilla/multiviews-v1120.xpi

The following error was encountered:

    * Access Denied.

Access control configuration prevents your request from being allowed at this
time. Please contact your service provider if you feel this is incorrect.

Your cache administrator is webmaster.
Generated Sat, 17 Aug 2002 11:38:00 GMT by squid1.nyc.access.net (Squid/2.4.STABLE6)

Comment 3

[Bjarne D Mathiesen]

Seems to be a problem at MozDev
Now I can't even install reinstall MozDev project in 20020722 that I've
previously successfully installed

An I'm not behind a proxy, so that's not an issue for me
I think they might have reconfigured their server incorrectly :-((

Comment 4

[Joshua C. Lerner]

I think it is some DNS issue. We updated downloads.mozdev.org yesterday - it 
points to a new host. Make sure your system thinks downloads.mozdev.org 
points to mozdev.secsup.org (208.209.50.17). In any case, the old invalid 
mapping should timeout if you wait a little longer. Sorry for the inconvenience.