by john.berthels:

What steps will reproduce the problem?

http://play.golang.org/p/hLyBQYF_W5


What is the expected output?
err1 <nil>
err2 <nil>
Cases handled the same


What do you see instead?
err1 mime: no media type
err2 <nil>
Cases handled differently

Which compiler are you using (5g, 6g, 8g, gccgo)?
6g

Which operating system are you using?
ubuntu linux 13.04

Which version are you using?  (run 'go version')
go version go1.1.2 linux/amd64


Please provide any additional information below.

We're in the process of replacing a production service with a re-implementation in
golang. This throws an error "mime: no media type" with POST requests from an
existing application. Investigation shows the POST lacks a content-type header, which
causes ParseForm to error.

My reading of RFC2616 section 7.2.1 suggests that a server should treat an absent
'Content-type' as 'application/octet-stream'.

ParseForm is being called, even though the input content-type is not
x-www-form-urlencoded, in wrapper code which wants to extract url parameters and/or form
parameters.

Looking at the code in net/http/request.go, I would think that parsePostForm should
return err=nil in the case of an absent content type. i.e. change:

   663      ct := r.Header.Get("Content-Type")
   664      ct, _, err = mime.ParseMediaType(ct)

to

   663      ct := r.Header.Get("Content-Type")
+               if ct == "" {
+                       return
+               }
   664      ct, _, err = mime.ParseMediaType(ct)


We're working around the problem, but I thought I'd report the issue for your
consideration.

regards,

jb