268653 - .pjpeg files invoke helper application instead of being opened in browser

Status: RESOLVED INVALID

(Firefox :: File Handling, defect)

Description

[Leonid Neishtadt]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When a .jpg file is uploaded through IE it comes with MIME type pjpeg. When such
is opened by IE, it is processed in the same way as jpg and jpeg. Firefox does
not recognize this type and invokes helper application.

Reproducible: Always
Steps to Reproduce:
Open the provide URL.

Actual Results:  
See that "Opening" dialog appears.

Expected Results:  
Try the same URL in IE/Netscape, else and the image is displayed inside the bowser.

Comment 1

[Matthias Versen [:Matti]]

The reason is that your server is not correct configured.
open http://web-sniffer.net , enter your URl and see the content type in the
response header.

Your server sends it as text/plain and that's wrong, your server should either
send it as image/pjpeg or image/jpeg

Comment 2

[Leonid Neishtadt]

(In reply to comment #1)
> The reason is that your server is not correct configured.
> open http://web-sniffer.net , enter your URl and see the content type in the
> response header.
> Your server sends it as text/plain and that's wrong, your server should either
> send it as image/pjpeg or image/jpeg


Thanks Matti.
I've added pjpeg to /etc/mime.types, restarted Apache, now web-sniffer shows 
HTTP response
Content-Type:	image/jpeg
but the problem persists.
Can you check again?

Comment 3

[Matthias Versen [:Matti]]

works now on win32 with Mozilla 20041110 :-)
You must clear the disk cache manually.There is a button for that in Mozilla but
don't know about Firefox but it should be under the privacy Tab in the options(?). 

The reason: Mozilla asks if the file changed but Apache reports that nothing
changed if you only change a mime-type. (and Mozilla use the old and wrong
mime-type from the disk-cache).

The reason why it works in IE: IE is broken and doesn't use mime-types from the
server (They break the RFCs) and they got many security problems with this...