Is NodeJS's https.get function/method asyncronous?

Russell R. — Sun, 06 Sep 2020 06:25:43 +0000

I was just wondering if the NodeJS https.get() method/function was asynchronous or not?

I'm still learning, but it seems like it is, since it was producing results before other code of mine, but I could be wrong.

Also, is https.get technically a function, or method? I wasn't sure when writing the title.

This is what I'm talking about:
https://nodejs.org/api/https.html#https_https_get_url_options_callback

SameSite Cookie Header and Google Login

Russell R. — Sun, 30 Aug 2020 03:29:08 +0000

I was recently experimenting with Login with Google for my own websites I develop, and came across this error (and change in the way Chrome handles cookies):

https://github.com/google/google-api-javascript-client/issues/561

From what I gather, soon Chrome will no longer accept cookies without this SameSite header. However, unless you disable this (via chrome://flags) in Chrome, right now, Login with Google doesn't seem to work.

So, is Chrome configured by default to block cookies without that header, and Google's "Login with Google" API isn't sending them with this header? Is that correct? If so, what do developers need to do, if anything, or is this something only Google needs to change?

Thanks. Been wondering about this for a few days now, and it's not 100% clear what's going on.

DEV Community: Russell R.

Is NodeJS's https.get function/method asyncronous?

SameSite Cookie Header and Google Login