296912 - Styles sometimes not applied when stylesheet returns HTTP 302

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[James Bennett]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Firefox/1.0.4 (Ubuntu package 1.0.2 MFSA2005-44)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050524 Firefox/1.0.4 (Ubuntu package 1.0.2 MFSA2005-44)

It seems that when a stylesheet returns an HTTP 302, Mozilla either does not
follow an HTTP 302 or takes the Content-Type header of the redirect to be the
Content-Type of the URI the redirect leads to.

In the example here, the referenced URI for the stylesheet is
http://usabilityworks.org/uwdotorg/styles.css, which returns an HTTP 302 (with
Content-Type 'text/html') redirecting to
http://usabilityworks.typepad.com/uwdotorg/styles.css (which sends the correct
Content-Type of 'text/css'). In my copies of Firefox and Mozilla the stylesheet
is not applied; I've had several other people try with various versions of
Firefox and the problem is not always reproducible -- some see styles applied
and some do not.

Reproducible: Sometimes

Steps to Reproduce:
1. Visit http://usabilityworks.typepad.com/ or any other site which returns an
HTTP 302 on the URI of its stylesheet.
Actual Results:  
Error: The stylesheet http://www.usabilityworks.org/uwdotorg/styles.css was not
loaded because its MIME type, "text/html", is not "text/css".

Expected Results:  
Follow the redirect and apply the stylesheet.

Comment 1

[Darin Fisher]

-> CSS

Comment 2

[Boris Zbarsky [:bzbarsky]]

Attachment: NSPR log of nsHttp:5,nsCSSLoader:5 for that page

Comment 3

[Boris Zbarsky [:bzbarsky]]

Darin, I don't see a 302 Found for the stylesheet in the log when I see the bug
(see attached log).  The relevant part of the log (I think) looks like this
(request and response matched up by the |this| pointer on nsHttpTransaction):

-1211902272[8072548]: nsHttpTransaction::Init [this=8910208 caps=1]
-1211902272[8072548]: http request [
-1211902272[8072548]:   GET /uwdotorg/styles.css HTTP/1.1
-1211902272[8072548]:   Host: www.usabilityworks.org
-1211902272[8072548]:   User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.8b2) Gecko/20050602 Firefox/1.0+
-1211902272[8072548]:   Accept: text/css,*/*;q=0.1
-1211902272[8072548]:   Accept-Language: en-us,en;q=0.5
-1211902272[8072548]:   Accept-Encoding: gzip,deflate
-1211902272[8072548]:   Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
-1211902272[8072548]:   Keep-Alive: 300
-1211902272[8072548]:   Connection: keep-alive
-1211902272[8072548]:   Referer: http://usabilityworks.typepad.com/
-1211902272[8072548]: ]
-1217287248[813cf78]: nsHttpTransaction::HandleContentStart [this=8910208]
-1217287248[813cf78]: http response [
-1217287248[813cf78]:   HTTP/1.0 200 OK
-1217287248[813cf78]:   Connection: Close
-1217287248[813cf78]:   Pragma: no-cache
-1217287248[813cf78]:   Cache-Control: no-cache
-1217287248[813cf78]:   Content-Type: text/html; charset=iso-8859-1
-1217287248[813cf78]: ]

I've only been able to reproduce the problem twice (on different machines at
that); since then every single load on either machine has shown the stylesheet
loading, even when I clear cache and then shift-reload.  In any case, I got the
problem with a Firefox build on machine A but not with a Mozilla build on the
same machine, and those weren't sharing a cache...

So it looks to me like this server just sends out bogus responses in some cases.
 In any case, the style system is just getting the wrong thing from necko here
for whatever reason, so it's not a style system bug.

Comment 4

[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 5

[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.