291366 - theme opens jar file instead of installing

Status: RESOLVED WORKSFORME

(mozilla.org :: FTP: Mirrors, task)

Description

[k]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

when i download the new theme it opens in firefox screen instead of installing
it... or confirming its installation as it happened in te last version.

Reproducible: Always

Steps to Reproduce:
1.Tools| themes| Get more theme | Abstract PC 0.9.7.5 for eg | Install
2.
3.

Actual Results:  
I see something like 
PK


Expected Results:  
Confirm dialog

Comment 1

[Matthias Versen [:Matti]]

wfm with FF1.0.3 on win2k3.
Reporter: Do you have extensions installed ?

Comment 2

[k]

(In reply to comment #1)
> wfm with FF1.0.3 on win2k3.
> Reporter: Do you have extensions installed ?
> 
> 

Yes...These were installed from earlier version.FF 1.0 and FF 1.0.1
Adblock, Flashgot, WeatherFox, Tabbrowser Prefs, Disable targets. 

Comment 3

[Matthias Versen [:Matti]]

Reporter:
Please close FF and run "firefox.exe -profilemanager" and create an additional
test profile. Now start FF with this test profile.

Comment 4

[k]

(In reply to comment #3)
> Reporter:
> Please close FF and run "firefox.exe -profilemanager" and create an additional
> test profile. Now start FF with this test profile.

I did that and have same result. I have additional information.If i go to Most 
Popular Firefox Themes at https://addons.update.mozilla.org/themes/ and click 
on the links from there it seems to work if i go to lets say top rated click on 
particular extension eg Noia 2.0 (eXtreme) 2.82 it gives me funky characters. 

Comment 5

[Matthias Versen [:Matti]]

I can confirm this now. It's a UMO or server bug ..
marking as dupe of bug 290637



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

Comment 6

[Matthias Versen [:Matti]]

There are many servers behind http://ftp.mozilla.org and near all of them send
the wrong mimetype (text/plain) for .jar files.

<justdave_> 204.152.184.113                text/plain
<justdave_> 205.188.221.241                text/plain
<justdave_> 216.165.129.134                text/plain
<justdave_> 64.12.204.21                   text/plain
<justdave_> 130.207.108.135                text/plain
<justdave_> 149.174.36.116                 text/plain
<justdave_> 156.56.247.196                 text/plain
<justdave_> 193.74.22.160                  application/x-java-archive
<justdave_> looks like only one of them is getting it right.


Mozilla does fix a text/plain from a default misconfigured server with such a
header "Content-Type: text/plain; charset=ISO-8859-1"

but one of the server (216.165.129.134) sends a different header:
"Content-Type: text/plain; charset=UTF-8" 
and Mozilla/Firefox displays this file as text/plain.

-> FTP Mirrors

Comment 7

[Dave Miller [:justdave]]

(In reply to comment #6)
> Mozilla does fix a text/plain from a default misconfigured server with such a
> header "Content-Type: text/plain; charset=ISO-8859-1"
> 
> but one of the server (216.165.129.134) sends a different header:
> "Content-Type: text/plain; charset=UTF-8" 
> and Mozilla/Firefox displays this file as text/plain.

Does that make this a Mozilla bug?  UTF-8 has been the default charset on new
installs of Apache for the last year or so.

Comment 8

[Matthias Versen [:Matti]]

Because of the many misconfigured servers bz added content sniffing for the
default apache setting with bug 220807. 
The default apache setting changed (different charset) and the content-type
sniffing fails now but we have bug 261263.

The server IS broken if it sends a .jar file as text/plain and the server should
be fixed. Content sniffing is always bad and all current users with FF1.0.X or
Mozilla 1.7.X would see this ugly problem on UMO

Comment 9

[Michael Morgan [:morgamic]]

Future themes and extensions will not have URIs with spaces in them -- they will be converted using a consistent rule so they are properly handled in URIs.

One of the causes of this text/plain problem is that the trigger was breaking for URIs with spaces in them.  This can be solved before they manifest by proper validation and naming conventions during file creation.  See bug 333391.