go to post Pasi Leino · Apr 12, 2017 Setting Authorization Basic header results Access-Control-Allow-Origin error.login:1 XMLHttpRequest cannot load http://<ens_host>:57773/csp/nnn/login. Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:4200' is therefore not allowed access.I have cors enabled in the service and the service works just fine with curl -H "Authorization: Basic <base64_coded_username_password>" urlSo it looks like Chrome wants to perform OPTIONS request in stead of plain GET and things go wrong there after and this might be a combination of many things. I anyone has any ideas, I would appreciate.-Pasi-
go to post Pasi Leino · Jun 5, 2016 Ah, sorry for not realizing this.However the latest FT 2016.3.0.628.0 does not include cache421.node. Nor does 2016.2 FT?!
go to post Pasi Leino · Jun 5, 2016 "Support for Node.js 4.2.x has been introduced with Caché 2016.2. If you grab a Windows field test kit you can find the binding file here: <install-dir>\bin\cache421.node."I can only find cache0100.node and cache0120.node there. I tried both FT:s 2016.2 and 2016.3.
go to post Pasi Leino · Jun 5, 2016 When will InterSystems update the cache.node module to support more current node 4 LTS?I was somewhat disapointed to see only the old cache0100.node and cache0120.node modules with the new fieldtest.
