I would suspect permanent, but who can say?
As I said in message 23 of that thread, no company today advertises what it has done or why or what they are really intending to do in the future for security reasons.
The problem is that browsers are getting to the stage where they use HTTPS as the default. In fact, I’ve even heard a rumour that Google will shortly discontinue support for HTTP all together. (Personally, I’ll believe that one when I see it).
That may be the driving force behind this change, as the Google engine is what powers a lot of modern browsers, including Edge, Brave & Chrome, etc.
This may be the first time you have encountered it, but this “not secure” warning is quite common on systems I’ve worked on over the years, and its origins go all the way back to 2017.
As I said, the important thing is to stop and think about what you are accessing in the context of the warning. If it’s an internal system, it doesn’t matter if the traffic is not encrypted. A lot of internal traffic on industrial systems is still not encrypted even today, because you automatically trust things inside your own network, so it doesn’t need the extra processing load of encryption and decryption.
