Timo Stark

@yosefy sorry to hear that you had such a bad experience! We are aware of this and we will work on better documentation and tooling for that!

Good morning! Yes, this was commited to njs in November 2023. The release of Version `0.8.2` we are currently using in Unit 1.32.0. See http://nginx.org/en/docs/njs/changes.html Due to breaking changes in...

Hi @TheFatal atm this is the way it is / was implemented but we are sure there is some space for improvement. I will flag this as an enhancement and...

Hi @micaelmalta sorry for the late response! Some things have changed on our end but I am happy to be back on things :) So what you are saying is...

Thanks @TokuiNico for sharing this! The root cause reported by @RomainMou needs still some investigation on our side. I would like to test this insight and outside the container. I...

This is still a very important feature / requirement but would mean we have to introduce the SSLClient side in NGINX Unit. This task has not beed started yet but...

Hi @pwtail thanks for reaching out and sorry for our late response! We were bussy shipping 1.32. We will have a look into this next week and come back with...

> Thanks for the feedback. > > > Inclusion at the global level would be appropriate. > > Yep, it makes sense to apply some of the options in the...

I have just looked into our internal documentation (Which I will move to Github - as there is no reason keeping the discussion about the way we want to work...

Thanks @txigreman for creating this issue. I followed the discussions and the issue that we are currently don't support dynamic values or values created by JavaScript functions in our `environment`...