287431 - Mozilla Update should download XPI, but says Invalid URI cannot Continue

Status: RESOLVED DUPLICATE of bug 290637

(addons.mozilla.org Graveyard :: Developer Pages, defect)

Description

[Martijn (MozBrowser.nl)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050305 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050305 Firefox/1.0+

When searching I thought that this bug was described in bug #275900. However,
the comments in that bug talk about MIMEtypes and possible patches to Firefox.
It should be fixed after Firefox-trunk, but I experience this with a Firefox
trunk-build (Gecko/20050305 Firefox/1.0+).
	


Reproducible: Always

Steps to Reproduce:
1. Try to download an extension for Thunderbird
2. Right click Install Now-link
3. Choose Save Target As...

Actual Results:  
Extension gets saved as a webpage (you actually download a file with just the
text "Invalid URI cannot Continue" inside).

Expected Results:  
Download the extension, ready to be installed in Thunderbird (as the procedure
tells people)

I think this is related to a space in the URI to the extension. I tested this
with Auto Copy (which has a space in the filename). Then I tried Mouse Gestures
(space in extension name, but no space in filename) and it succeeded. Then I
tried to Quote Colors (space in filename again) and this failed.
It looks like the install.php-script checks the filename (to prevent some
URL-insertion tricks ?) and thinks that this is not right.

The actual result is that a user tries downloading an extension, follows the
procedures and as a result the downloaded file is not a valid extension. I do
not know whether this is related to Firefox also. I only tested with
Thunderbird-extension because someone mentioned that they were downloaded as
webpage instead of an extension.

Comment 1

[alanjstr]

Maybe related to bug 286765 

Comment 2

[Martijn (MozBrowser.nl)]

(In reply to comment #1)
> Maybe related to bug 286765 

Yes, I think so. It sounds like the second patch for that bug will solve this
problem. I did not think that that bug was about this problem also, but now it
seems so.

Comment 3

[alanjstr]

*** This bug has been marked as a duplicate of 290637 ***