KeyError on expected headers

[asyncee]

KeyError on expected headers

[asyncee]

Hi!

The W3C Protocols page states:

Now that both HTTP extensions and HTTP/1.1 are stable specifications (RFC2616 at that time), W3C has closed the HTTP Activity.

So I assume that RFC2616 takes preference over RFC1341.

RFC2616 states that default media type should be application/octet-stream

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".

What do you think?

[asyncee]

Also, aiohttp client uses RFC2616 to set default content type if it is not specified so i think it's best to provide same behaviour between clients.

[coderfromhere]

Sure, my only goal regarding this issue is to make tracebacks clearer than just KeyError, the actual implementation of a safer alternative to content_type=response.headers["Content-Type"] can be borrowed from either spec/library.