218953 - Intermittent erroneous reporting of incorrect MIME type.

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[ChristopherBalz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624

In the page at the URL above, I have gotten intermittant reporting of an error
that the style sheet in question is not loaded since its MIME type is text/plain
and not text/css.  This happens even though, as shown below, I demonstrate that
the server is sending the page with the correct MIME type.  SHIFT-RELOADs on the
Mozilla 1.4 Web browser and restarts of the Web server did not immediately
correct the problem.  Unfortunately, this problem is intermittant, and so is
harder to pin down.  However, it definitely seems that something is not quite
right with MIME type sensing on http headers, at least with CSS style sheets.

In this situation, an HTML 'link' tag that links to the style sheet is
dynamically written as part of a dynamically generated (on the Web browser) HTML
document to a browser window frame (HTML frame in a frameset).  I would use the
HTML 'import' tag but prior versions of Mozilla have had bugs around this tag,
even though those browsers should never have been released as non-experimental
Web browsers (doing more damage to open Web standards than 'other' Web browsers
possibly could).  Since CSS stylesheets do not apply across frames, this is
necessary under some Web development architectures.

~/lynx http://treelogic-swe.com:8080/phraseologic/static/canvas.css -head -dump
HTTP/1.0 200 OK
Content-Type: text/css
Content-Length: 174
Last-Modified: Thu, 11 Sep 2003 07:12:33 GMT
Date: Thu, 11 Sep 2003 16:18:46 GMT
Server: Tomcat Web Server/3.3.1 Final ( JSP 1.1; Servlet 2.2 )

BODY {
    background-image: url(http://treelogic-swe.com:8080/phraseologic/static/bac
kground_tile_beige_small.jpg);
    margin-left: 20px;
}
.PrimitiveRefresh {
}



 TLSWE-LAPTOP-A0  Thu Sep 11 09:08:24
~/


Reproducible: Sometimes

Steps to Reproduce:
1.Build simple style sheet.
2.Write an HTML document to a window sub-frame that loads the style sheet via an
HTML 'link' tag.
3.Make sure that the Web server does _not_ have the correct MIME type setting
for css.  Open the HTML document on the Web browser, thus importing the CSS file.
4. Change the MIME setting to be correct on the server and then open the HTML
document again in the Web browser.

Actual Results:  
The Web browser at first correctly rejected the css style sheet because it had
an improper MIME type.  Then the Web browser incorrectly rejected the css style
sheet when its MIME type was indeed set correctly by the Web server, despite
closing the Web browser and re-starting it, and despite reloading the Web page
with shift-reload.  Finally, after shutting down Windows 2000 in a hibernation
and restarting, Mozilla loaded the css file, apparently finding that the css
file had the correct MIME type.

Expected Results:  
Mozilla should have detected that the MIME type was correct as soon as it was
correct and thus should have loaded the css file when in fact the css file did
come with the correct MIME type.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Over to networking.  The style system just uses whatever Necko reports.

If there is something you can do to make the problem reproducible, that would be
much appreciated; at the moment, all that happens is we look at the content-type
header your server returned; if that's wrong, chances are that it's a server
issue.  I just tried reloading your page a number of times with 1.5b on Win98,
and was not able to get the error you mention...

Comment 2

[ChristopherBalz]

As originally reported, the server was returning the correct MIME type for this 
file:

~/lynx http://treelogic-swe.com:8080/phraseologic/static/canvas.css -head -dump
HTTP/1.0 200 OK
Content-Type: text/css

If it works with 1.5b, the bug probably was fixed.  I was testing this with 1.2 
or 1.3.

 - CB

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.