Closed Bug 161656 Opened 21 years ago Closed 12 years ago - msdn does not send as a 404


(Tech Evangelism Graveyard :: English US, defect)

Windows 2000
Not set


(Not tracked)



(Reporter: timeless, Unassigned)




... something tells me we did the wrong thing here.
nop - he has a <base href="somewhere as MSDN">
Wrong in the way it displays in the JS Console?
If not maybe the site is showing the stylesheet of MIME type text/html
bah. I hate having to explain myself. ok, here's what's happening:
mozilla 2002080508 w32
There's a page on msdn which references a style sheet.
Google sent me something like a copy of that msdn page.
Mozilla tried to resolve the stylesheet, it managed to present a url to the msdn
webserver which triggered a 404.  MSDN responded with a 404 html error.
Mozilla ignored that it was an error page (and that it was text/html) and
decided that the author obviously wanted the 404 text/html error page to be used
as a style sheet (text/html). Mozilla warns me that it's doing something stupid.
I filed a bug.
I'll rephrase, cos I'm a dumbass and that last comment took me far too long to 

In quirks mode, Mozilla does not require that stylesheets are served as 
text/css.  In strict mode, a non-text/css stylesheet will be ignored.

The warning is letting you know that the stylesheet will be loaded even though 
it is the 'wrong' MIME type.

However, the stylesheet is the HTML result of a 404 error page - the stylesheet 
doesn't exist.  We shouldn't issue an error or attempt to parse the stylesheet 
if the stylesheet wasn't found.  (Note: I don't know if we *do* try to parse 
the HTML page as a stylesheet, but we certainly issue an error).

Is that right?
yeah. and for my comment it should have said "style sheet (text/css)" it's early.
i'm pretty sure we do display it, otherwise we wouldn't bother warning, or the
warning would be worded differently (it did say "stylesheet ... was loaded").

someone might want us to load a 404 text/css stylesheet, but that's not what
What build are you using?  Was it from before bug 112644 was fixed?
Ack.  Got it.
The page that the stylesheet refers to generates a 302 Moved to  That page is a 200 OK, not a 404 
Not Found, and it happens to be an HTML error page.

So, resolve as INVALID or reassign to evang, because we're doing the 'right' 
thing (although Microsoft aren't, arguably).

I've checked locally, and we definitely do not load (or warn about) stylesheets 
that are delivered with a genuine 404 return.
->invalid.  See previous comment.
Closed: 21 years ago
Resolution: --- → INVALID
i'd prefer to evangelize.
Component: Style System → US General
Product: Browser → Tech Evangelism
Resolution: INVALID → ---
Summary: Warning: The stylesheet was loaded as CSS even though its MIME type, "text/html", is not "text/css". → msdn does not send as a 404
Version: other → unspecified
can we ask them to send out a 404 header?
Assignee: dbaron → susiew
QA Contact: ian → zach
Ever confirmed: true
Keywords: evang500
Blocks: MS
tech evang june 2003 reorg
Assignee: susiew → english-us
QA Contact: zach → english-us
Summary: msdn does not send as a 404 → - msdn does not send as a 404
INCOMPLETE due to lack of activity since the end of 2009.

If someone is willing to investigate the issues raised in this bug to determine whether they still exist, *and* work with the site in question to fix any existing issues, please feel free to re-open and assign to yourself.

Sorry for the bugspam; filter on "NO MORE PRE-2010 TE BUGS" to remove.
Closed: 21 years ago12 years ago
Resolution: --- → INCOMPLETE
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.