[raxi]

Exactly those PIC18 devices, still in production and on sale, w/o any changes during the years: http://utronix.se/

Of course, no https, but.. it is not a platform limitation, just an undemanded feature: how would you get a https cert for 192.168.0.1 or a similar intranet address where those device suppose to work? They are just not for cloud datacenters

[Filligree]

You can make an HTTPs certificate with that in the SAN section, and it should work fine. You can't get one from a publicly trusted provider, of course, but that's fine; you don't own the IP.

In other words, make your own certificate authority for your own machines. It isn't that hard.

[raxi]

The problems here is not that hardness, and not even yearly certificate updates, or bothering with new certs on every IP address change, but (as the commentator above rightly pointed out)...

1. Planned obsolescence built into HTTPS: no HTTPS-aware server device from year 1999 would work with 2023 browsers. Just because "too old crypto". Plain HTTP works.

Being on a buy side I am against HTTPS in such devices, but I understand the sell side's position.