I spent most of the weekend migrating to Windows Server 2019, coming from Windows Server 2016. I didn't really have a reason to do so other than to dip my toes into Server 2019, and to be on the latest and greatest. Everything went pretty smooth, mostly, so now I'm on Server 2019.
In the process of migrating to Windows Server 2019, I decided to use my handy-dandy Windows 10 Cleaner PowerShell script..., and found out that it had a bug. Once I finished the migration, I dove into figuring out what was causing the bug. It turned out that my HTML minifier middleware was minifying every response, regardless of its content type. After a few hours, I fixed it to only minify
text/html responses, and the script is now being sent correctly. Yay!
Lastly, after the migration, I found out that Visual Studio 2017 FTP publishing over TLS is ancient and only supports up to TLS 1.0. I'm not happy about it because I was really trying to get to an A+ rating on SSL Labs, but I couldn't simply so I can publish from within Visual Studio. Really not happy about it. If anyone runs into an issue like that, you have to at least have the
TLS_RSA_WITH_AES_256_CBC_SHA (0x35) cipher enabled on your server, if you have control of that. Microsoft, please update and fix the FTP publishing in Visual Studio 2019 to support TLS 1.2 and higher!