Hi ​@Marco Maat,

In development and test I would also recommend using HTTPS. Besides security, using HTTPS enables browsers to use HTTP2, which greatly boosts performance.
When production is using HTTPS and test and development aren't, the performance characteristics aren't comparable and thus you don't have a representative test and development environment.

Kind regards,
Leroy Witteveen 

​@Leroy Witteveen  Thanks for your answer. But that was not the question. 

​@Marco Maat 

Fair enough, to directly answer your original question, it isn't possible to disable this warning.

Kind regards,
Leroy Witteveen

​@Marco Maat, not entirely sure but my best guess is that in your universal gui client folder on the webserver there are a few javascript files that contain the variable secure_connection_required which do some magic stuff to popup warnings and errors. Most probably the _next/static/chunks directory.

Alter those files and you probably get rid of the warning/error. 

Though I still would advice the thingy ​@Leroy Witteveen mentioned tbh. Maybe the time you spent on changing the files is about the same to get https running maybe...

​@Ricky  

Creative find, but by editing Universals’ JavaScript you make it harder for us to diagnose crashes as Sentry won't be able to match the minified sourcecode to the original sourcecode anymore, so I would strongly advise against this.

Kind regards,
Leroy Witteveen

​@Leroy Witteveen Yes, I mainly if not always suggest to develop your things leaning against a production situation and not tinker with things that are not yours to begin with. This way you will encounter problems early in the development phase instead of when your users are encountering it. If this means we’d have to setup and maintain an entire and complete infrastructure, it has proven to be worth the hassle.

In this case the changes you’d make would be nullified with the next upgrade anyway. Better to setup the certificates for https and so on once and benefit from this along the way.