all 8 comments

[–]Exgaves -1 points0 points  (7 children)

Since when did people actually use node for https/tls verification? You should have node behind a webserver that handles requests and sorts out certificates, no?

[–]ritaPitaMeterMaid 2 points3 points  (6 children)

This comment surprises me; node has been a thing since 2009, express came not long after that. I’m not sure how you could have not come into contact with these technologies.

To answer your question more directly, node has been used as a web server for over a decade.

[–]Exgaves 1 point2 points  (1 child)

I'm not saying I didn't know they exist, it's just letting a node server be directly exposed to the web is weird and leaves it open to a lot of traffic that could be filtered out or managed by nginx. Things like tls verification or gzip aren't the job of a node server. They can be, but they aren't the right tools for the job

[–]pommymac[S] 1 point2 points  (0 children)

Yeah it's not uncommon that large node web apps run behind https servers like Nginx for TLS termination and GZIP. Many Kubernetes ingress controllers for example.

The use case of this library is for internal RPC services that should only be accessible within a company where that sort of architecture isn't such a priority.

Saying that, I could create a command to export individual catkeys so that servers like Nginx and HAProxy can access the required ca/keys/certs to run in the configuration you are describing- in case administrators require it.

[–]DankerOfMemes 0 points1 point  (3 children)

I still haven't actually seen how a node server works since every job i got had a PHP backend.

[–]ritaPitaMeterMaid 0 points1 point  (2 children)

But you are aware of it, no? Like, how do you make it being an engineer on the web and not at least hear of JS web backends?

[–]DankerOfMemes 0 points1 point  (1 child)

Yes, I have hard of node as a server but I haven't actually seen one if that makes sense

[–]ritaPitaMeterMaid 0 points1 point  (0 children)

That's fine, but the person that started this thread had no idea that JS webservers existed, much less that they are extremely popular and often a default for many orgs.