Fix broken content_type

[zoffixznet]

Currently, setting content_type is ignored. This change fixes it. There's no need to set text/html as default in render method because it's set to that value elsewhere.

[ufobat]

Thank you!

You are right. I am not even sure if defaulting it to "text/html" is even a good idea. Maybe a generic "application/octet-stream" is best.

It might help for this fallback as well.

According to the RFC

Any HTTP/1.1 message containing an entity-body SHOULD include a
Content-Type header field defining the media type of that body. If
and only if the media type is not given by a Content-Type field, the
recipient MAY attempt to guess the media type via inspection of its
content and/or the name extension(s) of the URI used to identify the
resource. If the media type remains unknown, the recipient SHOULD
treat it as type "application/octet-stream".
-- RFC2616

[zoffixznet]

I am not even sure if defaulting it to "text/html" is even a good idea.

But then all routes would have to explicitly set Content Type. Considering a Web Framework is to server text/html pages, I think the current default is sane.