This bug has been fixed in apt-transport-https 1.2.19 (xenial) and 1.3.4 (yakkety), released 2017-01-26, by Julian Klode in bug 1651923.
If you are still affected by it, update apt-transport-https to the appropriate version and reinstall Ubuntu's version of ttf-mscorefonts-installer. You should remove Debian's version of ttf-mscorefonts-installer beforehand, if you installed it (unless you want to keep using Debian's version of course).
If you run into Content-Range errors when reinstalling ttf-mscorefonts-installer, remove the downloaded fonts in /var/lib/update-notifier/package-data-downloads/partial/ and try again. This is a different bug, also fixed recently, but not backported to Xenial and Yakkety yet (bug 1657567).
This bug has been fixed in apt-transport-https 1.2.19 (xenial) and 1.3.4 (yakkety), released 2017-01-26, by Julian Klode in bug 1651923.
If you are still affected by it, update apt-transport-https to the appropriate version and reinstall Ubuntu's version of ttf-mscorefonts -installer. You should remove Debian's version of ttf-mscorefonts -installer beforehand, if you installed it (unless you want to keep using Debian's version of course).
If you run into Content-Range errors when reinstalling ttf-mscorefonts -installer, remove the downloaded fonts in /var/lib/ update- notifier/ package- data-downloads/ partial/ and try again. This is a different bug, also fixed recently, but not backported to Xenial and Yakkety yet (bug 1657567).