That’s great, but i went to and couldn’t locate the ‘feature request’ system. however i found a feature request topic on the forum (http://forum.mikrotik.com/t/several-questions/1029/1) where you also mention the confusion when deciding where exactly a request should be made. I thought to myself on the new system there should be votes, and i got to vote for this feature ![]()
The client-side X.509 support in this container should work – that part is more complex to setup, but likely worth figuring out. Since the X509 certs are pass-thru from OS’s keystore/keychain, makes browser+CORS pretty safe and streamlined. Only issue with the container for this… is that it’s needs to know a username/password(s) to proxy after X509 auth in nginx, which isn’t ideal.
Excuse me, I did’t understand, this part properly. Are you suggesting me an laternative? or give other details about your solution?