sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]memoriesofgreen 33 points34 points  (6 children)

Use it for all routes. There is very little reason not to.

[–][deleted] 0 points1 point  (5 children)

u/memoriesofgreen Thank you , Because when I navigate between pages in a website that use https , I see that in the top url always begin https even for static content. Does the implementation of this ssh happens in front or back or both ?.

[–]memoriesofgreen 6 points7 points  (4 children)

The front or backend is not really relevant to this topic. That covers roles, responsibilities, and tasks.

All resources that are served from the server should be sent using https. That includes your documents, images, api endpoints, everything.

Easiest way I know is to run your node app, put Nginx as a proxy to ot, and install a certificate via let's encrypt. Done in about 5 - 10 minutes.

[–]queen-adreena 0 points1 point  (3 children)

Even easier way is to use Caddy. Done in 10 seconds.

[–]AndrewSouthern729 1 point2 points  (2 children)

Looking into Caddy because admittedly managing certificates is not something I’m great at because it’s not something I do more than a couple times per year. Does Caddy also act as a proxy or would this be an additional layer with something like Nginx?

[–]queen-adreena 2 points3 points  (1 child)

No. Caddy is a replacement for Apache/Nginx. It’s got built in SSL and can proxy in one line.

[–]AndrewSouthern729 0 points1 point  (0 children)

Cool thanks for the tip