Jiwa

Mike.Sheen wrote:

SBarnes wrote:but what if something needs to stay on http?

Then that something can't participate on the internet.

We allow non HTTPS only for the ease of development and testing, but really in this day and age if anything can't do HTTPS then they might as well pack up their things and go home.

Probably correct and as for all routes loading you could always get around that not only with the ability to allow and deny routes at the user level but you could always have extra insurance by a request filter as an option as well to look at incoming ips, port, routes etc. so nothing slipped through.

Is there any update on the status of this?

SBarnes wrote:Is there any update on the status of this?

It's still about 70% done - been that way for about 8 months now... not had a chance to get back onto it.

We're planning on this being included in 7.3 of Jiwa - but we've not been able to work on that for some time - we hope to be able to get our focus back onto that in the next few months - so end of year is currently a realistic timeframe.

Thanks, is that ETA the same for 7.3 as well or would the api be separate?