161656 - microsoft.com - msdn does not send http://msdn.microsoft.com/404/default.asp as a 404

Status: RESOLVED INCOMPLETE

(Tech Evangelism Graveyard :: English US, defect)

Description

[timeless]

... something tells me we did the wrong thing here.

Comment 1

[Kai Lahmann (is there, where MNG is)]

nop - he has a <base href="somewhere as MSDN">

Comment 2

[Ian Neal]

Wrong in the way it displays in the JS Console?
If not maybe the site is showing the stylesheet of MIME type text/html

Comment 3

[timeless]

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.

Comment 4

[Malcolm Rowe]

I'll rephrase, cos I'm a dumbass and that last comment took me far too long to 
understand.

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?

Comment 5

[timeless]

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

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

What build are you using?  Was it from before bug 112644 was fixed?

Comment 7

[Malcolm Rowe]

Ack.  Got it.
The page that the stylesheet refers to generates a 302 Moved to 
http://msdn.microsoft.com/404/default.asp.  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.

Comment 8

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

->invalid.  See previous comment.

Comment 9

[timeless]

i'd prefer to evangelize.

Comment 10

[timeless]

can we ask them to send out a 404 header?

Comment 11

[Bob Clary [:bc] (inactive)]

tech evang june 2003 reorg

Comment 12

[Chris Lawson (gone)]

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.