61066 - Mime type incorrectly detected

Status: VERIFIED DUPLICATE of bug 80313

(Core :: Networking: HTTP, defect, P3)

Description

[Gilles Durys]

Try to load the url : Mozilla will ask you to save the Pcgittb.exe file.
Looking at the response header, I see that the mime-type is text/html so it
shouldn't offer to save the file.
Works fine in Netscape4.x though.

Comment 1

[Gilles Durys]

Hmm... I should take a break sometimes.
Forgot to say I'm using 2000112220 trunk on winnt4

Comment 2

[Boris Zbarsky [:bzbarsky]]

Hmm...  looking at the return from the server:

~% telnet 193.121.180.17 80
Trying 193.121.180.17...
Connected to 193.121.180.17.
Escape character is '^]'.
GET
/scripts/Pcgittb.exe?langue=0&idO_r=1000220&idD_r=1000203&idV_r=0&hh=10&mn=40&j=23&m=11&a=2000&DoA=0&reseau=sncb&nombre=0
HTTP/1.0

HTTP/1.1 200 OK
Server: Microsoft-IIS/4.0
Date: Thu, 23 Nov 2000 14:31:32 GMT
Content-type : text/html

The Content-Type header name is misspelled (should be an uppercase Type) and
there is a space between "Type" and ":"

I believe that this is an invalid header per RFC 1945 and should be ignored by
Mozilla....  If so, that CGI needs to be fixed.

Comment 3

[tenthumbs]

RFC2616 section 4.2 says header names are case-insensitive. I belive rfc1945
says something similar. That's not the problem. The space probably is, though.

Comment 4

[Asa Dotzler [:asa]]

over to Networking.  

Comment 5

[Gagan]

Per the spec the trailing spaces are not valid characters in the token for the 
headers. Marking as WONTFIX.

Comment 6

[Bradley Baetz (:bbaetz)]

This was fixed as part of bug 80313, even though I believe that the space is
invalid. Andreas, which part of the spec says that this is legal? Theres nothing
wrong with being a liberal in what we accept, though.

Reopening, but feel free to close it again if you think that what we do now is
OK.

Comment 7

[Andreas M. "Clarence" Schneider]

RFC 2616, 2.1/2.2:

-8<-----

   implied *LWS
      The grammar described by this specification is word-based. Except
      where noted otherwise, linear white space (LWS) can be included
      between any two adjacent words (token or quoted-string), and
      between adjacent words and separators, without changing the
      interpretation of a field.

[...]

       LWS            = [CRLF] 1*( SP | HT )

-8<-----

Exceptions to this rule include request line, status line and media types.

Marking dupe of bug 80313.

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

Comment 8

[benc]

VERIFIED/dupe