mime: TypeByExtension is case sensitive

[reusee]

What does 'go version' print?
go version devel +a5e45f250654 Wed Jul 09 13:17:27 2014 +1000 linux/amd64

What steps reproduce the problem?
http://play.golang.org/p/hYEP_A3Ie9

What happened?
"type: "

What should have happened instead?
"type: image/jpeg"

[jeffallen]

Comment 1:

I understand this request and I agree in principle. But when I looked for a
specification saying these should be case insensitive, I could not find it. Can you
point out one?

[davecheney]

Comment 2:

rfc2045:
"   The type, subtype, and parameter names are not case sensitive.  For
   example, TEXT, Text, and TeXt are all equivalent top-level media
   types.  Parameter values are normally case sensitive, but sometimes
   are interpreted in a case-insensitive fashion, depending on the
   intended use.  (For example, multipart boundaries are case-sensitive,
   but the "access-type" parameter for message/External-body is not
   case-sensitive.)
The rest of the rfc details in the bnf grammar which comparisons are case sensitive and
which are not.

Labels changed: added release-none, repo-main.

Status changed to Accepted.

[bradfitz]

Comment 3:

That's talking about the case sensitivity of mime types, not file extensions, no?

[davecheney]

Comment 4:

I am sorry, I mistook this issue for one about mime type case sensitivity.

[reusee]

Comment 5:

File extension is not strictly defined in any specification but in some other
widely-used language / platform it's case insensitive.
apache http://httpd.apache.org/docs/current/mod/mod_mime.html "The extension argument is
case-insensitive"
python https://docs.python.org/2/library/mimetypes.html "type suffixes are first tried
case sensitively, then case insensitively"

[gopherbot]

Comment 6:

CL https://golang.org/cl/127380043 mentions this issue.

[bradfitz]

Comment 7:

If anything, I think we should do what Python does in comment #5. That doesn't appear to
be what Patchset 3 of https://golang.org/cl/127380043 implements.

[bradfitz]

Comment 8:

This issue was closed by revision af12dc5.

Status changed to Fixed.