153920 - OBJECT tag does not work with embedded documents or images if the content-type header needs to be checked. Only works if TYPE attribute or file extension is not missing

Status: VERIFIED DUPLICATE of bug 96579

(Core Graveyard :: Plug-ins, defect, P2)

Description

[Peter Lubczynski]

Problem:
The OBJECT tag is supposed to work like an IFRAME to embed documents. Using the
TYPE attribute, it foces us up front into creating a subdocument. However, this
is completely broken if we determine the mime type late in the game from the
content-type header. 

Testcase:
<object data="http://www.mozilla.org" width=400 height=400>Alternate</object>

I suspect the same is true for images. :(

Possible fix:
In |nsPluginStreamListenerPeer::OnStartRequest|, where we call
|mHost->SetUpPluginInstance(aContentType.get(), aURL, mOwner)|, we should
probably be doing the same check for images and documents that is found in
|nsObjectFrame::Init|.

Comment 1

[Peter Lubczynski]

Attachment: document testcase using OBJECT tag

Comment 2

[Peter Lubczynski]

In analyzing these numbers:
http://praline.netscape.com/admin/source/apps/report/plugin/reports/
...it appears that Netscape 7.x is sending many people to the PFS for mime-types
that it can handle internally:
text/html
text/plain
image/gif

This should not happen. Gecko is perfectly able to render those mime-types so I
think some of that data may be caused by this bug.

Comment 3

[Gregg Landskov (gone)]

I have always wondered about why those mime-types show up...another one is
octet-stream, I thought the browser can handle that one as well.

The other confusing thing is that 4.x hits to the pfs show the same mime-types
(text/html, image/gif, etc.).

It would be great to get this fixed.  Do you have a clear understanding on why
this happens?

Comment 4

[Peter Lubczynski]

Attachment: testcase with EMBED tag showing bug going to the PFS for a text/html MIME type

Well, we already have code to check for a TYPE= attribute and file extension
and replace that tag with an IFRAME or IMG frame. The code that gets the
mime-type from the server does not currently have the ability to trigger the
IFRAME/IMG replacement, so I bet it's sending users to the PFS. Take a look at
this testcase using the EMBED tag which will direct users to the PFS for
text/html.

Comment 5

[Peter Lubczynski]

nominating nsbeta1, server logs show thousands of people hitting this

Comment 6

[rubydoo123]

added impact and nsbeta1+

Comment 7

[Hixie (not reading bugmail)]

I'm not very familiar with <object> bugs but to me this looks like a duplicate
of bug 96579.

Comment 8

[Christopher Hoess (gone)]

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

Comment 9

[shrirang khanzode]

mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"