I'm not sure this is a bug but rather a sane modification to aiohttp to add default Content-Type headers as application/octet-stream. Throughout the tests in both aiohttp server & client it's asserted to be application/octet-stream when unset. This change was made upstream here.
I've opted to patch the tests here by adopting this convention of using application/octet-stream but also specifying it explicitly so that it still works with older versions.
Fixes #32
I'm not sure this is a bug but rather a sane modification to aiohttp to add default Content-Type headers as
application/octet-stream
. Throughout the tests in both aiohttp server & client it's asserted to beapplication/octet-stream
when unset. This change was made upstream here.I've opted to patch the tests here by adopting this convention of using
application/octet-stream
but also specifying it explicitly so that it still works with older versions.