Refining the Unsupported Media Type validation

It turns out that some browsers might send a Content-Type even if there
is no request body.  I changed the logic to check if there is any
content instead of checking if a Content-Type header was passed.